Book Image

Java EE 8 Development with Eclipse - Third Edition

By : Ram Kulkarni
Book Image

Java EE 8 Development with Eclipse - Third Edition

By: Ram Kulkarni

Overview of this book

Java EE is one of the most popular tools for enterprise application design and development. With recent changes to Java EE 8 specifications, Java EE application development has become a lot simpler with the new specifications, some of which compete with the existing specifications. This guide provides a complete overview of developing highly performant, robust and secure enterprise applications with Java EE with Eclipse. The book begins by exploring different Java EE technologies and how to use them (JSP, JSF, JPA, JDBC, EJB, and more), along with suitable technologies for different scenarios. You will learn how to set up the development environment for Java EE applications and understand Java EE specifications in detail, with an emphasis on examples. The book takes you through deployment of an application in Tomcat, GlassFish Servers, and also in the cloud. It goes beyond the basics and covers topics like debugging, testing, deployment, and securing your Java EE applications. You'll also get to know techniques to develop cloud-ready microservices in Java EE.
Table of Contents (20 chapters)
Title Page
Copyright and Credits
Dedication
Packt Upsell
Free Chapter
1
Introducing JEE and Eclipse
Index

Dependency injection


Spring MVC is a part of the overall Spring Framework. The core feature of the Spring Framework is dependency injection (DI). Almost all other features of the Spring Framework use DI. Objects managed by the dependency injection framework are not directly instantiated in the code (using, for example, the new operator). Let's call them managed objects. These objects are created by a DI framework, such as Spring. Because these objects are created by a framework, the framework has a lot more flexibility in deciding how to set values in the object and from where to get them. For example, your Data Access Object (DAO) class might need an instance of a database connection factory object. However, instead of instantiating it in the DAO class, you just tell the DI framework that when it instantiates the DAO, it has to set the value of a member variable for the connection pool factory. Of course, the parameters for the connection pool factory will have to be configured somewhere...