[CONF] OpenJPA: Integration (page edited)

[confluence]

Page Edited : openjpa : Integration Integration has been edited by Donald Woods (Apr 24, 2009). Change summary: initial pass at runtime depends (View changes) Content: Runtime Dependencies The binary release download of OpenJPA includes all of the code needed to run in a stand-alone Java SE JVM or within a Java EE application server. For example, the OpenJPA 1.2.1 release download apache-openjpa-1.2.1-binary.zip includes the following required OpenJPA artifact under apache-openjpa-1.2.1/: \ openjpa-1.2.1.jar and the following required runtime dependencies under apache-openjpa-1.2.1/lib/: commons-collections-3.2.jar commons-lang-2.1.jar commons-pool-1.3.jar serp-1.13.1.jar The following artifacts under lib/ are only needed for Java SE environments, as a Java EE application server should provide an implementation: geronimo-jpa_3.0_spec-1.0.jar geronimo-jta_1.1_spec-1.1.jar The following is optional, as you should include the JDBC driver artifacts required by your database provider and supported by OpenJPA: derby-10.2.2.0.jar Integrating with Apache Geronimo: Apache Geronimo V2.0.2 through 2.1.3 include OpenJPA 1.0.x and you can simply deploy an enterprise archive, web archive, or EJB-JAR that contains a persistence unit. Apache Geronimo V2.1.4 includes OpenJPA 1.2.x and you can simply deploy an enterprise archive, web archive, or EJB-JAR that contains a persistence unit. Integrating with GlassFish: Since GlassFish implements the Java Persistence API 1.0 SPI, it is very easy to use OpenJPA in Glassfish. See Sahoo's blog for further details. Integrating with Sun Java System Application Server 9.x: Since Sun Java System Application Server is based on code from the GlassFish project, the instructions to use OpenJPA in GlassFish and Sun Java System Application Server remain the same. Integrating with IBM WebSphere Application Server: See IBM WebSphere Developer Technical Journal: Leveraging OpenJPA with WebSphere Application Server V6.1. Also, WebSphere Application Server V6.1 can download and install the EJB3 Feature Pack, which includes OpenJPA 1.0.x. WebSphere Application Server V7.0 includes OpenJPA 1.2.x and you can simply deploy an enterprise archive, web archive, or EJB-JAR that contains a persistence unit. Integrating with IBM WebSphere Application Server Community Edition: WebSphere Application Server Community Edition V2.0.0.2 through 2.1.1.1 include OpenJPA 1.0.x and you can simply deploy an enterprise archive, web archive, or EJB-JAR that contains a persistence unit. WebSphere Application Server Community Edition V2.1.x releases after V2.1.1.1 will include OpenJPA 1.2.x and you can simply deploy an enterprise archive, web archive, or EJB-JAR that contains a persistence unit. Integrating with JOnAS Application Server V 4.X (J2EE 1.4 / EJB2.1 Container): OpenJPA can successfully be integrated with the JOnAS 4.x Application server family. I succeeded in configuring OpenJPA to use managed JTA transactions of JOnAS, which means that you can use OpenJPA in parallel to EJB 2.1 CMP/BMP Entity Beans within the SAME container managed transactions of your JOnAS Application Server. See Hans Prueller's blog entry for further details. Integrating with BEA Weblogic Server 10: BEA WebLogic Server 10 includes OpenJPA. To use OpenJPA in a WebLogic Server environment, you can simply deploy an enterprise archive, web archive, or EJB-JAR that contains a persistence unit. The default persistence provider in WebLogic Server is OpenJPA + Kodo, so you can either leave the <provider> element out of your persistence.xml file, or set it to org.apache.openjpa.persistence.PersistenceProviderImpl. BEA Kodo is built on top of OpenJPA, and so includes the OpenJPA jars.

Powered by Atlassian Confluence (Version: 2.2.9 Build:#527 Sep 07, 2006) - Bug/feature request

Unsubscribe or edit your notifications preferences