Community
Participate
Working Groups
>The tutorial on the different methods of what architectures involving EclipseLink on WebSphere 7 needs to be updated. - start with scenarios that modifiy the server like creating a global shared library and end with EAR based eclipselink libraries that are solely in the control of the developer. http://wiki.eclipse.org/EclipseLink/Examples/JPA/WebSphere_Web_Tutorial#Global_Scoped_Datasource_Setup - Container Managed - @PersistenceContext injection on stateless session bean or servlet via @EJB injection - Application managed - via Persistence.createEntityManagerFactory() static bootstrap - verify whether dynamic weaving is enabled in both CM and AM cases - verify JPA 2.0 functionality and how a mixed JPA 1.0/JPA 2.0 production system functions
>Bug # 261671 may benefit from different classloader levels during this investigation
>Also verify (bug# 246126 like) javax.persistence.jtaDataSource override for application managed EARs
Created attachment 165341 [details] EAR for a container managed @PersistenceContext injection on a stateless session bean of a eclipselink jpa deployment - servlet based: ear requires replacement of EAR/app-inf/lib/eclipselink.jar >The following EAR will deploy a container managed persistence unit Note: because of upload attachment limitations - I have temp removed the eclipselink.jar from the EAR in org.eclipse.persistence.example.jpa.server.websphere.EnterpriseEAR\APP-INF\lib\eclipselink.jar - you need to add this or a newer eclipselink.jar library back and repackage the EAR. >URL http://127.0.0.1:9080/enterprise/FrontController?action=demo&rnd=.04393939420 >prepopulate the database with the following SE JPA ddl-gen persistence unit app http://dev.eclipse.org/svnroot/rt/org.eclipse.persistence/trunk/examples/org.eclipse.persistence.example.jpa.server.common.ddlgen/ >Documentation http://wiki.eclipse.org/EclipseLink/Examples/JPA/WebSphere7_Web_Tutorial#Container_Managed_EclipseLink_library_in_EAR
>closing down this bug and wiki edits - as the 3 container managed scenarios are prototyped, documented and working for eclipselink JPA on WebSphere 7 >we can reopen this bug if application managed scenarios require expansion. >no server modification http://wiki.eclipse.org/EclipseLink/Examples/JPA/WebSphere7_Web_Tutorial#Container_Managed_EclipseLink_library_in_EAR >server modifications required http://wiki.eclipse.org/EclipseLink/Examples/JPA/WebSphere7_Web_Tutorial#EclipseLink_library_in_Server.2Flib http://wiki.eclipse.org/EclipseLink/Examples/JPA/WebSphere7_Web_Tutorial#EclipseLink_library_as_Global_Shared_Library
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
