- Full Description
Beginning Database-Driven Application Development in Java EE: Using GlassFish focuses on the open source GlassFish persistence engine. This book shows Java programmers how to develop applications utilizing relational database technologies with examples using Oracle and MySQL and the GlassFish application development framework and deployment platform all based on Java EE.
- The book explains in detail how you can organize your Java EE solution into a multilayer architecture, placing most emphasis on how to implement the persistence and database tiers of an application.
- Through many examples, this book shows how you can efficiently use the Java Persistence features available in the Java EE platform. Find out how you can greatly simplify the task of building the persistence layer of your Java EE application by moving some application logic into the underlying database, utilizing database views, stored programs, and triggers.
- The book also explains how to deploy Java EE applications to GlassFish, a free, open source Java EE 5compliant application server.
What youll learn
- Use the GlassFish persistence layer in conjunction with GlassFish Java EE application server.
- Organize the database and persistence tiers of a Java EE application and utilize MySQL or Oracle database applications when building the database tier.
- Work with EJB 3 JPA object/relational mapping features, plug JPA into Java EE transactional environment, and implement persistence with the EJB 3 EntityManager.
- Integrate and use JSF (webtier) using GlassFish JSF Framework (Scales) and other JSF tools/frameworks.
- Deploy applications to GlassFish Application Server.
Who this book is for
The book is appropriate for Java developers who want to learn how to develop Java EE applications interacting with a relational database via the Java Persistence API (JPA) and then deploy them to the open source GlassFish Application Server.
- Source Code/Downloads
Please Login to submit errata.On page 64:Just before "Testing the Application," you have:
# jar cvf ..\dist\hellowrodlapp.jar .
As a result, the thelloworldapp.jar file should appear in the HelloWorldEJB/dist directory.
But the last directory we were in was HelloWorldProject\target\META-INF
So it seems instruction to change directory before running this command is left out. From the steps leading up to this, I think the jar would really be built in HelloWorldProject/dist, not HelloWorldProject/HelloWorldEJB/dist.