Community
Participate
Working Groups
>Currently the same object model is duplicated among all the EJB project for WebSphere, JBoss, WebLogic, OC4J and the SE DDL generation project >this will require a small persistence.xml and .project .classpath refactor for all existing EAR tutorials in SVN - We move these entities to an entity only jar project - We reference the jar in the EAR JEE dependencies - We select the project in the EJB project dependency - adding it to the MANIFEST.MF as Class-Path: org.eclipse.persistence.example.jpa.server.entities.jar - We optionally reference the jar in the persistence.xml for each ejb project <jar-file>org.eclipse.persistence.example.jpa.server.entities.jar</jar-file>
Created attachment 165586 [details] Common entities.jar <jar-file> for persistence.xml for all WebSphere, WebLogic, OC4J, JBoss and SE DDL example projects
>prototyped - however there may be issues with the target-server tag for various EE servers - using 2 levels of persistence.xml
>For WAR only EAR's on GlassFish V3 - this may be the only way the persistence unit is parsed by the web container (separate entity jar) - to verify
>WebLogic EAR with (ejb.jar (SSB only and persistence.xml), WAR and entity.jar (entities only)) running on WebLogic 10.3.3.0
Created attachment 178770 [details] Common entities.jar <jar-file> for persistence.xml for all WebSphere, WebLogic, OC4J, JBoss and SE DDL example projects
>See SVN rev# 8171 containing common entities project and EAR changes for WebLogic https://fisheye2.atlassian.com/changelog/eclipselink/?cs=8171 - JBoss, WebSphere, OC4J, Glassfish pending - improved client and datamodel pending
>cancelled
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink