Difference between revisions of "EclipseLink/Examples/JPA/GlassFishV3 Web Tutorial"
m (→Install GlassFish)
m (→Install GlassFish)
|Line 35:||Line 35:|
GlassFish V3 the jars the .
*Using GlassFish V3 Prelude we run into jar naming conflicts.
*Using GlassFish V3 Prelude we run into jar naming conflicts .
|Line 50:||Line 46:|
Revision as of 13:50, 11 September 2008
EclipseLink JPA Deployed on GlassFish 3 using Eclipse WTP
Note: This tutorial' is under construction for the next week as of 20080909.
If you want to get a small web application running quickly on GlassFish - the services provided by the Web Tools Project pluggin in the Eclipse IDE can take care of the deployment details and set the server into debug mode for you.
This basic example details how to use Eclipse to run/debug a minimum J2EE web application servlet using EclipseLink JPA as the persistence provider. The goal of this example is to detail the minimum steps needed to run EclipseLink inside GlassFish using the Eclipse IDE - at this point no presentation/controller layer such as JSF, Spring or Struts will be used beyond a basic HttpServlet so we can concentrate on the the integration layer JPA setup.
The DALI project was used to generate Entities from a schema with sequences already populated.
This example will run fine with Eclipse 3.3 EE and any Database that EclipseLink supports.
Install Eclipse EE
- I installed a clean version of Eclipse Ganymede M5 with all of WTP 3.0
Install a Database
- In this example I am using Oracle 11g, the table schemas have already been created manually and all entitity java classes have been generated using the Eclipse DALI tool.
- Do not use V3 TP2 - use the V3 Prelude release instead.
- See the following quickly solved issues posted to the GlassFish forum
- See the following GlassFish Technology Preview 2 page.
- Note V3TP2 is currently a subset of JEE5 but it has everything we need JSF 1.2, JSP 2.1/Servlet 2.5 and JPA 1.0 via EclipseLink
- Using GlassFish V3 TP2 install - the jars are named 10.0-tp-2-SNAPSHOT - but the plugin expects 10.0-SNAPSHOT
- Using GlassFish V3 Prelude install - we run into jar naming conflicts - solved below.
- However, A workaround is to use the snapshot plugin which matches with the jar names in Prelude except for a missing javax.management.j2ee-10.0-SNAPSHOT.jar which you can stub, get from another server or create from the tp2 javax.javaee-10.0-tp-2-SNAPSHOT.jar
All of deployment, JNDI setup, persistence.xml configuration, jpql query example - in progress ......