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

Chapter 7. Creating JEE Applications with EJB

In the last chapter, we learned some techniques to debug JEE applications from Eclipse. In this chapter, we will shift our focus back to JEE application development and learn how to create and use Enterprise JavaBeans (EJB). If you recall the architecture of database applications in Chapter 4, Creating JEE Database Applications, we had JSP or a JSF page calling a JSP bean or a managed bean. The beans then called DAOs to execute the data access code. This separated code for the user interface, the business logic, and the database nicely. This would work for small or medium applications, but may prove to be a bottleneck in large enterprise applications; the application may not scale very well. If processing of the business logic is time consuming then it would make more sense to distribute it on different servers for better scalability and resilience. If code for the user interface, the business logic, and the data access is all on the same machine...