Jump to: navigation, search

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

m (EclipseLink JPA Deployed on OC4J using Eclipse WTP)
m (Quick Start Notes)
Line 3: Line 3:
 
== Quick Start Notes ==
 
== Quick Start Notes ==
 
*The following summary lists the essential changes required (beyond what is shipped out of the box) to get running up quickly for advanced users.
 
*The following summary lists the essential changes required (beyond what is shipped out of the box) to get running up quickly for advanced users.
**1) Add a new ''org.eclipse.persistence'' shared-library containing the 2 jars required to run EclipseLink JPA
+
**1) Add a new [[EclipseLink/Examples/JPA/OC4J_Web_Tutorial#Option_1:_Add_an_eclipselink_shared-library_to_OC4J_-_recommended|''org.eclipse.persistence'' shared-library]] containing the 2 jars required to run EclipseLink JPA
 
**2) Either create a new 10.1.3 server in Eclipse and deploy your EAR there, or deploy your EAR manually via the EM console.
 
**2) Either create a new 10.1.3 server in Eclipse and deploy your EAR there, or deploy your EAR manually via the EM console.
  

Revision as of 16:08, 26 February 2009

Contents

EclipseLink JPA Deployed on OC4J using Eclipse WTP

Quick Start Notes

  • The following summary lists the essential changes required (beyond what is shipped out of the box) to get running up quickly for advanced users.
    • 1) Add a new org.eclipse.persistence shared-library containing the 2 jars required to run EclipseLink JPA
    • 2) Either create a new 10.1.3 server in Eclipse and deploy your EAR there, or deploy your EAR manually via the EM console.

Document History

Date Author Version Description & Notes
20080414 Michael O'Brien Initial version covering Oracle OC4J 10.1.3.4 and 11.1.1.0
20090217 Michael O'Brien Update for version 10.1.3.5 or 10.1.4 - In progress as of 20090223

If you want to get a small web application running quickly on OC4J use the services provided by the Web Tools Project plugin in the Eclipse IDE to take care of deployment details 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 OC4J 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.

Tutorial Source

The EAR, EJB and WEB Eclipse project source for this EclipseLink OC4J tutorial are available online at the following locations. These 3 projects must be imported along with the jpa core eclipselink project.

  • Checkout the following 3 projects together from $trunk/examples.
    • org.eclipse.persistence.example.jpa.server.oc4j.enterpriseEAR
    • org.eclipse.persistence.example.jpa.server.oc4j.enterpriseEJB
    • org.eclipse.persistence.example.jpa.server.oc4j.enterpriseWeb
  • EclipseLink source via SVN committer access

svn+ssh://user@eclipse/svnroot/rt/org.eclipse.persistence/trunk

  • EclipseLink source via SVN anonymous access

svn://dev.eclipse.org/svnroot/rt/org.eclipse.persistence/trunk

The following link will put you at the root of the SVN tree using the online version of subclipse.

http://dev.eclipse.org/svnroot/rt/org.eclipse.persistence/trunk/examples/org.eclipse.persistence.example.jpa.server.oc4j.enterpriseEAR

http://dev.eclipse.org/svnroot/rt/org.eclipse.persistence/trunk/examples/org.eclipse.persistence.example.jpa.server.oc4j.enterpriseEJB

http://dev.eclipse.org/svnroot/rt/org.eclipse.persistence/trunk/examples/org.eclipse.persistence.example.jpa.server.oc4j.enterpriseWeb

And the DDL generation J2SE JPA application used to populate the database schema.

http://dev.eclipse.org/svnroot/rt/org.eclipse.persistence/trunk/examples/org.eclipse.persistence.example.jpa.server.common.ddlgen

Development Environment

Hardware: Windows Vista SP1, Core2Duo E8400 45nm, 3.0Ghz, 3Gb Ram

Software: Eclipse IDE for Java EE 3.4 Ganymede (SR1 Oct 2008), Oracle 11g DB 11.1.0.6.0, Java JDK 1.6.0_07, OC4J 10.1.3.4.0 20080709

This example will run fine with any DB that EclipseLink supports via the eclipselink.target-database tag.

Prerequisites

Install Eclipse

  • I installed a clean version of Eclipse Ganymede EE SR1 Version: 3.4.1 Build id: M20080911-1700 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 entity java classes have been generated using the Eclipse DALI tool.

Install OC4J 10.1.4

C:\opt\oc4j1014
Where 
OC4J_HOME=C:/opt/oc4j1014/j2ee/home
ORACLE_HOME=c:/opt/oc4j1014

Verify OC4J Installation

  • Before we add EclipseLink and our own JTA datasource to OC4J, lets verify the installation outside of eclipse before adding the server to the IDE.

Start OC4J the first time Outside Eclipse

  • If this is the first time you are running your OC4J server, you will want to login from a CMD prompt - to set the admin password.
  • The ORACLE_HOME environment variable should also be set to a truncated OC4J_HOME or c:\opt\oc4j1014
  • Launch server via CMD prompt - and create your admin password.
C:\opt\oc4j1014\bin>oc4j -start
Starting OC4J from c:\opt\oc4j1014\j2ee\home ...
2009-02-18 14:15:03.406 NOTIFICATION Auto-unpacking C:\opt\oc4j1014\j2ee\home\applications\dms.war...
...
Feb 18, 2009 2:15:09 PM com.evermind.server.XMLApplicationServerConfig randomizeJtaAdminPassword
INFO: Updating JtaAdmin account
09/02/18 14:15:09 Set OC4J administrator's password (password text will not be displayed as it is entered)
Enter password:
Confirm password:
The password for OC4J administrator "oc4jadmin" has been set.
09/02/18 14:15:21 The OC4J administrator "oc4jadmin" account is activated.
09/02/18 14:15:27 Oracle Containers for J2EE 10g (10.1.3.5.0)  initialized

Verify OC4J HTTP 8888 and ORMI 23791 ports are running

C:\opt\oc4j1014\bin>netstat -a
  TCP    0.0.0.0:8888           mfobrien-PC3:0         LISTENING
  TCP    0.0.0.0:23791          mfobrien-PC3:0         LISTENING

Oc4j em admin welcome screen.jpg

Verify that OC4J shutdown works fine

  • Open a separate cmd prompt and shutdown the server.
C:\opt\oc4j1014\bin>oc4j -shutdown -port 23791 -password password
Shutdown OC4J instance...
C:\opt\oc4j1014\bin>
  • Observe that oc4j is shutdown in the original CMD prompt.
09/02/18 14:38:22 Shutting down...
C:\opt\oc4j1014\bin>

OC4J configuration Changes

  • OC4J ships with a default JTA datasource called OracleDS that points to an Oracle DB install on the same machine.
  • Use or Edit the OC4J config in $OC4J_HOME/config/data-sources.xml and enter the following DataSource definition for JTA and non-JTA sources and refering to it in the managed-data-source. The only thing you may need to change is the IP address 127.0.0.1 if your database server is on another machine, the user, password and schema name orcl.
  <managed-data-source name="OracleDS" connection-pool-name="local oracle11g" jndi-name="jdbc/OracleDS"/>
  <connection-pool name="local oracle11g">
    <connection-factory factory-class="oracle.jdbc.pool.OracleDataSource"
      user="user"
      password="password"
      url="jdbc:oracle:thin:@//127.0.0.1:1521/orcl">
    </connection-factory>
  </connection-pool>

Oc4j em admin data sources url.jpg

Note: If you modify a JDBC datasource using the EM UI - the data-sources.xml will be completely regenerated and any commented elements will be overwritten - if you would like to keep them then edit data-sources.xml manually.

EclipseLink JAR location

The OC4J 10.1.3 release does not ship with the EclipseLink JPA provider - you will need to create a shared library to pick up the jars.

There are 2 jar files required to run the EclipseLink provider on OC4J - eclipselink.jar and a version of the specification jar - currently javax.persistence_2.0_preview.jar.

eclipselink.jar on the Server or EAR?

  • It is not recommended that you distribute eclipselink.jar with your EAR application in a production environment.
  • Why? One reason is that an application deployed EclipseLink jar will be lower on the server ClassLoader tree and will not be available to other modules or applications higher up due to hierarchical visibility constraints. However, there may be occasions during development or staging that you will want to run a local copy or different version than the one loaded from the modules directory - I have not tested this scenario yet, a test of the 3 use cases will be required.

Option 1: Add an eclipselink shared-library to OC4J - recommended

  • In this OC4J configuration step we will create a versioned shared-library for EclipseLink and reference any dependent jars in the xml config files.

Add eclipselink shared-library to config.xml

  • Get the following jars ready for your EclipseLink shared library
  • Create a new eclipselink directory off of $OC4J_ROOT at the same level as the existing toplink directory.
  • Edit $OC4J_HOME/config/server.xml and add the following shared-library element above the existing oracle.persistence.
	<shared-library name="org.eclipse.persistence" version="2.0" library-compatible="true">
		<!-- EclipseLink core jar - either of the following jars are ok -->
		<code-source path="../../../eclipselink/jlib/eclipselink.jar"/>		
		<!--code-source path="../../../eclipselink/jlib/org.eclipse.persistence_1.0.0.0_1-1-0.jar"/-->
		<!-- JPA 1.0 or JPA 2.0 specification jar - one of the following -->
		<code-source path="../../../eclipselink/jlib/javax.persistence_2.0_preview.jar"/>
		<!--code-source path="../../../eclipselink/jlib/javax.persistence_1.0.0.0_1-0-2.jar"/-->
		<import-shared-library name="oracle.jdbc"/>
	</shared-library>

Add EclipseLink shared-library to system-application.xml

  • Add the following import-shared-library element above the existing two shared libraries oracle.persistence and oracle.toplink in $OC4J_HOME/config/system-application.xml around line 30.
  <imported-shared-libraries>
    <import-shared-library name="org.eclipse.persistence"/>
    <import-shared-library name="oracle.toplink"/>
    <import-shared-library name="oracle.persistence"/>

Option 2: Modify the toplink/jlib shipped module - not recommended

  • As of OC4J Server 10.1.3.5 / 10.1.4 the TopLink essentials library is shipped in the following location on the server.
  • Theoretically you could replace the jars and rename the library but I would not recommend this approach.
    • $OC4J_ROOT/toplink/jlib/toplink.jar (I am running rev 2.0.0.20090218-SNAPSHOT)

oracle.persistence shared library

  • Since OC4J 10.1.3.1.0 a shared-library element has been shipped with the server config - this library is not used by this example.
  • In $OC4J_HOME/config/server.xml the following configuration for the shared library oracle.persistence is setup.
	<shared-library name="oracle.persistence" version="1.0" library-compatible="true">
		<code-source path="../../../toplink/jlib/toplink-essentials.jar"/>
		<import-shared-library name="oracle.jdbc"/>
	</shared-library>
  • There is also an empty directory for toplink that can be ignored.
$OC4J_HOME\applications\ascontrol\ascontrol\ias\oc4j\toplink

Option 3: eclipselink.jar in applib - not recommended

The approach will work fine for most configurations however placing eclipselink.jar in the applib directory will put it lower in the classpath than creating a shared-library in option 1.

The eclipselink.jar may be placed as noted by config/server.xml in the directory $OC4J_HOME/applib or in my case C:\opt\oc4j1014\j2ee\home\applib

  <!-- Global application libraries -->
  <shared-library name="global.libraries" version="1.0" library-compatible="true">
    <code-source path="../applib"/>
  </shared-library>

This approach will not allow you to easily version different distributions of EclipseLink - like you are able to using a shared-library via the version tag, in option 1.

However if you go the route of using the applib directory then you will need to also put a version of javax.persistence.*.jar as well as a version of the jdbc jar your database requires - in my case orai18n.jar or ojdbc14.jar.

Otherwise you will see the following missing JDBC jar CNFE on your first entityManager interaction with the database.

09/02/26 13:23:16 javax.ejb.EJBException: java.lang.NoClassDefFoundError: org/eclipse/persistence/internal/platform/database/oracle/TIMESTAMPTypes
09/02/26 13:23:16 	at com.evermind.server.ejb.EJBUtils.getLocalUserException(EJBUtils.java:337)

You will see the following on startup...TBD


Option 4: eclipselink.jar specified at startup - not recommended

TBD. If you want to reference eclipselink.jar outside of the OC4J install then you must modify the startup script that was generated for your domain.

see $OC4J_ROOT/bin/oc4j.cmd:183 appended to the following line.

"%JAVA_HOME%\bin\java" %JVMARGS% -jar "%OC4J_JAR%" %CMDARGS% 

javax.persistence.jar

  • EclipseLink supports JPA 1.0 and a preview of JPA 2.0, this jar is shipped in $OC4J_ROOT/toplink/jlib where $OC4J is c:/opt/oc4j1014 in my case.

JDBC JAR location

  • There is an existing Oracle jdbc driver in OC4J_HOME/../jdbc/lib/orai18n.jar
  • Or, copy your specific jdbc driver jar to $OC4J_HOME/applib

Create server in Eclipse

Open the servers view New | Server | Oracle | Oracle OC4J Standalone Server 10.1.3.n (it is ok to use this one for 10.1.4). The only default you may need to change is the admin user from oc4jadmin to fmwadmin.

Eclipse oc4j server setup 2.jpg

Update in progress 20090223 past this point...

Verify OC4J server launch from Eclipse

You will see the following after starting the server from the servers' tab - no TopLink product interaction happens yet.

09/02/26 09:55:00 Oracle Containers for J2EE 10g (10.1.3.5.0)  initialized

Create J2EE application

Check out the 3 example projects in the trunk '(TBD) or create your own J2EE Enterprise Application as below. File | new | project | J2EE | Enterprise Application Project Select server, use 5.0 Ear version

Create a new Web and an optional EJB project

Select generate deployment descriptor if you want to change the context-root

  • Path changes
	<classpathentry combineaccessrules="false" kind="src" path="/eclipselink.core"/>
	<classpathentry combineaccessrules="false" kind="src" path="/eclipselink.jpa"/>
  • After EAR project creation - reference eclipselink.core and eclipselink.jpa or include a reference to eclipselink.jar in your WAR project.
  • If you don't reference the eclipselink.* projects then include a classpath reference to persistence.jar and an Oracle JDBC driver jar for your DB - You will need to put this JDBC driver jar in your OC4J applib directory as well.

UML Data Model

The following single entity Cell has a @ManyToMany bidirectional relationship to itself.

Eclipselink server jee jpa examples datamodel.gif

Tutorial Design

The goal of the tutorial is to demonstrate a quick start end-to-end deployment on a specific application server of an EclipseLink JPA application. To accomplish this...

  • The web framework is a simple servlet so we avoid container specific issues around JSF implementation.
  • The data model is very simple (@ManyToMany) - as the other tutorials get into more advanced JPA entity concepts and annoations
  • The entitymanager is container managed where possible by injection
  • The schema is generated by DDL generation in a separate common application

managed SE app.

  • The application context name is standard across servers
  • The datasource is globally defined (by the user) on the server - with the only configuration setting being the jta-data-source element in persistence.xml

DDL/Schema Generation

Persistence.xml

JTA Datasource

  • JTA : Put persistence.xml beside your JPA entities in yourProjectEJB/ejbModule/META-INF
  • Note: Your <jta-data-source> or <non-jta-data-source> element in persistence.xml must match the JNDI Name: on the server admin page Home >Summary of JDBC Data Sources - either prefixed with jdbc/ or not.


<persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
  <persistence-unit name="unifiedWebLogic" transaction-type="JTA">
    <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
    <jta-data-source>OracleDS</jta-data-source>         
    <non-jta-data-source>OracleDS</non-jta-data-source>
    <properties>
      <property name="eclipselink.target-server" value="WebLogic_10"/>
      <property name="eclipselink.logging.level" value="FINEST"/>
    </properties>
  </persistence-unit>
</persistence>

RESOURCE_LOCAL Datasource

  • RESOURCE_LOCAL : non-JTA : Put persistence.xml beside your JPA entities in yourProjectEJB/ejbModule/META-INF
<persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
  <persistence-unit name="unifiedWebLogic" transaction-type="RESOURCE_LOCAL">
    <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
    <properties>
      <property name="eclipselink.target-server" value="WebLogic_10"/>
      <property name="eclipselink.logging.level" value="FINEST"/>
      <property name="eclipselink.jdbc.driver" value="oracle.jdbc.driver.OracleDriver"/>
      <property name="eclipselink.jdbc.platform" value="org.eclipse.persistence.platform.database.oracle.OraclePlatform"/>
      <property name="eclipselink.jdbc.url" value="jdbc:oracle:thin:@localhost:1521:orcl"/>
      <property name="eclipselink.jdbc.user" value="user"/>
      <property name="eclipselink.jdbc.password" value="pw"/>
    </properties>
  </persistence-unit>
</persistence>

persistence.xml

  • Put persistence.xml in yourProjectEJB/ejbModule/META-INF
<persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
    <persistence-unit name="statJPAJ2EE" transaction-type="JTA">
       <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
        <non-jta-data-source>jdbc/OracleDS</non-jta-data-source>
        <class>org.eclipse.persistence.example.navigation.business.StatClass</class>
… other entity classes
        <properties>
            <property name="eclipselink.target-server" value="OC4J"/>
            <property name="eclipselink.weaving" value="true"/>
            <property name="eclipselink.logging.level" value="FINEST"/>
        </properties>       
    </persistence-unit>
</persistence>

J5EE: Container Managed Persistence

  • Inject the Session Bean (DAO) and the EntityManager via
@Local
@Stateless
public class ApplicationService implements ApplicationServiceLocal {
	@PersistenceContext(unitName="statJPAJ2EE")	
	private EntityManager entityManager;

and...
public class FrontController extends HttpServlet implements Servlet {
	@EJB
	public ApplicationService applicationService;

J2SE: Application Managed Persistence

  • Put persistence.xml in yourProjectWeb/src/META-INF
<persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
    <persistence-unit name="statJPAJ2EE" transaction-type="RESOURCE_LOCAL">
       <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
        <non-jta-data-source>jdbc/OracleDS</non-jta-data-source>
        <class>org.eclipse.persistence.example.navigation.business.StatClass</class>
… other entity classes
        <properties>
            <property name="eclipselink.target-server" value="OC4J"/>
            <property name="eclipselink.logging.level" value="FINEST"/>
        </properties>       
    </persistence-unit>
</persistence>

Start Server=

  • Steps: Select the EAR and [Run on Server].
  • The first "Run on Server" may not start the server, in this case you "Start Server" and then "Run on Server".

Publish EAR

  • Eclipse WTP will take care of dynamically generating all the orion*.xml files required by OC4J when you either [re-publish] or modify any files while the server is running.
  • You may also use any combination of running the OC4J server yourself in run or debug mode and using eclipse to publish EAR changes.
  • In the predeploy EAR Ant task you should see weaving messages for your entities if logs are set to FINEST in persistence.xml
  • Depending on your application you will see the following after running [start server]
    • In your console window you will see two processes - one for the server and the second for the deploy target.
Oracle OC4J SA Server 11.1.1.0.0 localhost [Generic Server]	
	C:\jdk1.5.0\bin\javaw.exe (Apr 9, 2008 9:06:19 AM)	
<terminated>jpaELTestEAR module publisher [Ant Build]	
	<terminated, exit value: 0>C:\jdk1.5.0\bin\javaw.exe (Apr 9, 2008 9:06:36 AM)	
  • If you click on the deploy target console you will see the deploy logs from the WTP oracle*.xml Ant target...
Buildfile: C:\eclipse34\plugins\org.eclipse.jst.server.generic.oc4j_1.5.105.v20071217\buildfiles\oracle.10.1.3.xml
check.skip.ear.deploy:
deploy.j2ee.ear:
package.module.ear:
      [jar] Building jar: C:\opt\oc4j11samba\j2ee\home\applications\jpaELTestEAR.ear
[oracle:deploy] Deploying application jpaELTestEAR.
...
[oracle:deploy] Application deployer for jpaELTestEAR COMPLETES.
  • If you click on the server console you will see the predeploy weaving logs
08/04/09 09:06:29 Oracle Containers for J2EE 11g (11.1.1.0.0)  initialized.
08/04/09 09:06:39 Application Deployer for jpaELTestEAR STARTS.
...
08/04/09 09:06:39 Started application : jpaELTestEAR
08/04/09 09:06:39 Binding jpaELTestWeb web-module for application jpaELTestEAR to site default-web-site under context root jpaELTest
[EPS Finest]: 2008.04.09 09:06:39.893--ServerSession(23543153)--Thread(Thread[DeployerRunnable Thread for jpaELTestEAR,9,SystemThreadGroup])--Begin predeploying Persistence Unit statJPAJ2EE; state Initial; factoryCount 0
...
[EL Finer]: 2008.04.09 09:06:39.940--ServerSession(23543153)--Thread(Thread[DeployerRunnable Thread for jpaELTestEAR,9,SystemThreadGroup])--Found a default mapping file at file:/C:/opt/oc4j11samba/j2ee/home/applications/jpaELTestEAR/jpaELTestWeb/WEB-INF/classes/META-INF/orm.xml for root URL file:/C:/opt/oc4j11samba/j2ee/home/applications/jpaELTestEAR/jpaELTestWeb/WEB-INF/classes/
...
[EL Finer]: 2008.04.09 09:06:40.783--ServerSession(23543153)--Thread(Thread[DeployerRunnable Thread for jpaELTestEAR,9,SystemThreadGroup])--Class [org.eclipse.persistence.example.navigation.business.StatClass] registered to be processed by weaver.
...
[EL Finest]: 2008.04.09 09:06:40.783--ServerSession(23543153)--Thread(Thread[DeployerRunnable Thread for jpaELTestEAR,9,SystemThreadGroup])--End predeploying Persistence Unit statJPAJ2EE; state Predeployed; factoryCount 1
[EL Finest]: 2008.04.09 09:06:41.033--ServerSession(23543153)--Thread(Thread[DeployerRunnable Thread for jpaELTestEAR,9,SystemThreadGroup])--Begin weaver class transformer processing class [org/eclipse/persistence/example/navigation/business/StatClass].
[EL Finest]: 2008.04.09 09:06:41.079--ServerSession(23543153)--Thread(Thread[DeployerRunnable Thread for jpaELTestEAR,9,SystemThreadGroup])--End weaver class transformer processing class [org/eclipse/persistence/example/navigation/business/StatClass].
...
08/04/09 09:06:41 Application Deployer for jpaELTestEAR COMPLETES. Operation time: 2155 msecs

Perform a JPQL query

  • At this time you can initialize your application in a browser - notice the use of the non-jta datasource
public class FrontController extends HttpServlet implements Servlet {
	@EJB(beanName="ApplicationService")
	public ApplicationServiceLocal applicationService;
...
 
@Local
public interface ApplicationServiceLocal {
...
 
@Local
@Stateless
public class ApplicationService implements ApplicationServiceLocal {
	@PersistenceContext(unitName="example")	
	private EntityManager entityManager;
...

Console Output

[EL Finest]: 2009-02-26 14:04:34.464--ServerSession(8634980)--Thread(Thread[HTTPThreadGroup-4,5,HTTPThreadGroup])--Begin deploying Persistence Unit example; state Predeployed; factoryCount 1
[EL Info]:   2009-02-26 14:04:34.542--ServerSession(8634980)--Thread(Thread[HTTPThreadGroup-4,5,HTTPThreadGroup])--EclipseLink, version: Eclipse Persistence Services - 2.0.0.20090218-SNAPSHOT
[EL Fine]:   2009-02-26 14:04:35.213--Thread(Thread[HTTPThreadGroup-4,5,HTTPThreadGroup])--Detected Vendor platform: org.eclipse.persistence.platform.database.oracle.Oracle10Platform
[EL Config]: 2009-02-26 14:04:35.26--ServerSession(8634980)--Connection(5230779)--Thread(Thread[HTTPThreadGroup-4,5,HTTPThreadGroup])--Connected: jdbc:oracle:thin:@//10.156.52.98:1521/ORCL
	User: SCOTT
	Database: Oracle  Version: Oracle Database 11g Release 11.1.0.0.0 - Production
	Driver: Oracle JDBC driver  Version: 10.1.0.5.0
[EL Finest]: 2009-02-26 14:04:35.385--UnitOfWork(5746770)--Thread(Thread[HTTPThreadGroup-4,5,HTTPThreadGroup])--PERSIST operation called on: org.eclipse.persistence.example.jpa.server.business.Cell@9107088( id: null state: null left: null right: null parent: null references: null).
[EL Fine]:   2009-02-26 14:04:35.807--ClientSession(5748500)--Connection(6653899)--Thread(Thread[HTTPThreadGroup-4,5,HTTPThreadGroup])--INSERT INTO EL_CELL (ID, STATE, TSEQ, RIGHT_ID) VALUES (?, ?, ?, ?)
	bind => [551, null, null, null]

Browser Output

The following screen capture of this quickstart JEE OC4J JPA application shows a visual representation of the entities persisted to the Oracle database using the EclipseLink JPA implementation on Oracle OC4J Server 10.1.3.5.

Eclipselink example jpa oc4j web jpql action cap.jpg

Troubleshooting

References