- Before reading this book, readers need to know about the object-oriented concept, the Java language, and the basic concepts of Java EE. In this book, we assume that the reader already knows some specifications of the Java EE umbrella, such as EJB, JPA, and CDI, among others.
- To test the code of this book, you need an application server that supports Java EE 8, such as GlassFish 5.0. Furthermore, you need to use an IDE such as IntelliJ, Eclipse, NetBeans, or any other that supports the Java language.
To get the most out of this book
Download the example code files
You can download the example code files for this book from your account at www.packtpub.com. If you purchased this book elsewhere, you can visit www.packtpub.com/support and register to have the files emailed directly to you.
You can download the code files by following these steps:
- Log in or register at www.packtpub.com.
- Select the SUPPORT tab.
- Click on Code Downloads & Errata.
- Enter the name of the book in the Search box and follow the onscreen instructions.
Once the file is downloaded, please make sure that you unzip or extract the folder using the latest version of:
- WinRAR/7-Zip for Windows
- Zipeg/iZip/UnRarX for Mac
- 7-Zip/PeaZip for Linux
The code bundle for the book is also hosted on GitHub at https://github.com/PacktPublishing/Java-EE-8-Design-Patterns-and-Best-Practices. In case there's an update to the code, it will be updated on the existing GitHub repository.
We also have other code bundles from our rich catalog of books and videos available at https://github.com/PacktPublishing/. Check them out!
Download the color images
We also provide a PDF file that has color images of the screenshots/diagrams used in this book. You can download it here: https://www.packtpub.com/sites/default/files/downloads/JavaEE8DesignPatternsandBestPractices_ColorImages.pdf.
Conventions used
There are a number of text conventions used throughout this book.
CodeInText: Indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles. Here is an example: "It is also important to bear in mind that the @Electronic qualifier identifies the decorated object."
A block of code is set as follows:
public interface Engineering {
List<String> getDisciplines ();
}
public class BasicEngineering implements Engineering {
@Override
public List<String> getDisciplines() {
return Arrays.asList("d7", "d3");
}
}
@Electronic
public class ElectronicEngineering extends BasicEngineering {
...
}
@Mechanical
public class MechanicalEngineering extends BasicEngineering {
...
}
When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:
@Loggable
@Interceptor
public class LoggedInterceptor implements Serializable {
@AroundInvoke
public Object logMethod (InvocationContext invocationContext) throws
Exception{
System.out.println("Entering method : "
+ invocationContext.getMethod().getName() + " "
+ invocationContext.getMethod().getDeclaringClass()
);
return invocationContext.proceed();
}
}
Any command-line input or output is written as follows:
creating bean.
intercepting post construct of bean.
post construct of bean
Bold: Indicates a new term, an important word, or words that you see onscreen. For example, words in menus or dialog boxes appear in the text like this. Here is an example: "After the user logs in, when they access Application 1, Application 2, or Application 3, they will not need to log in again. "