Jump to: navigation, search

Difference between revisions of "EclipseLink/Examples/JPA/GlassFishV3 Web Tutorial"

m (Install GlassFish)
m (Install GlassFish)
Line 23: Line 23:
  
 
====<font color="green">Install GlassFish</font>====
 
====<font color="green">Install GlassFish</font>====
 +
*Do not use V3 TP2 - use the [http://download.java.net/glassfish/v3/promoted/ V3 Prelude release] instead.
 +
*See the following quickly solved issues posted to the GlassFish forum
 +
[http://forums.java.net/jive/thread.jspa?threadID=46886&tstart=0 GF3tp2 domain1 fails to start out of the box - JDK 1.7 collision and no proxy set]
 +
[http://forums.java.net/jive/thread.jspa?threadID=46901&tstart=0 GlassFish V3 SNAPSHOT Server Plugin for Eclipse 3.4 jar problems with TP2 - use the Prelude Plugin]
 +
 +
 
*See the following [https://glassfish.dev.java.net/downloads/v3-techPreview-2.html GlassFish Technology Preview 2 page].
 
*See the following [https://glassfish.dev.java.net/downloads/v3-techPreview-2.html GlassFish Technology Preview 2 page].
 
*Note V3TP2 is currently a [http://wiki.glassfish.java.net/Wiki.jsp?page=GlassFishV3TP2Content subset of JEE5] but it has everything we need JSF 1.2, JSP 2.1/Servlet 2.5 and JPA 1.0 via EclipseLink
 
*Note V3TP2 is currently a [http://wiki.glassfish.java.net/Wiki.jsp?page=GlassFishV3TP2Content subset of JEE5] but it has everything we need JSF 1.2, JSP 2.1/Servlet 2.5 and JPA 1.0 via EclipseLink
 +
  
 
All of Installation, deployment, JNDI setup, persistence.xml configuration, jpql query example - in progress ......
 
All of Installation, deployment, JNDI setup, persistence.xml configuration, jpql query example - in progress ......

Revision as of 13:47, 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.

Development Environment

Software: Eclipse IDE for Java EE 3.4 M5 Ganymede (Feb 2008) with all 5 packages (DTP 1.6, EMF 2.4, GEF 3.4, WTP 3.0, XSD 2.4), Oracle 11g DB 11.1.0.6.0, Java JDK 1.5.0_11, GlassFish 3.0 TP2

This example will run fine with Eclipse 3.3 EE and any Database that EclipseLink supports.

Prerequisites

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.

Install GlassFish

  • Do not use V3 TP2 - use the V3 Prelude release instead.
  • See the following quickly solved issues posted to the GlassFish forum

GF3tp2 domain1 fails to start out of the box - JDK 1.7 collision and no proxy set GlassFish V3 SNAPSHOT Server Plugin for Eclipse 3.4 jar problems with TP2 - use the Prelude Plugin



All of Installation, deployment, JNDI setup, persistence.xml configuration, jpql query example - in progress ......

I am currently working past the following issue with the GlassFish V3 SNAPSHOT plugin to Eclipse 3.4. The workaround is to rename the jars and create stubs for the missing ones to get past the creation errors and then rename them back once we have a server instance.

  • Using GlassFish V3 TP2

New server jar version errors.JPG

  • Using GlassFish V3 Prelude we run into jar naming conflicts.

Glassfish prelude new server jar version errors.JPG

  • 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

Glassfish prelude new server javax mgmt missing.JPG