Community
Participate
Working Groups
The 3 EAR, EJB and WEB Eclipse 3.4 projects used to write the JBoss JPA EAR application (container managed) tutorial will be checked in and updated against this enhancement request. DDL Schema Generation: All the application server tutorials for EclipseLink use a common shared data model (currently using a single @ManyToMany for simplicity). To aide in database schema setup, the enhancement bug# 250473 contains the [org.eclipse.persistence.example.jpa.server.common] Java SE application that performs DDL generation for all JPA container tutorials. 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 see http://wiki.eclipse.org/EclipseLink/Examples/JPA/JBoss_Web_Tutorial The example has been up for around 5 months with 2300 hits
>Retest on JBoss 5.0 GA >Retest SessionCustomizer requirement - looks like we no longer need it and are running fine on JBoss with COMPOSITE_NAME_LOOKUP
Updating priority due to revised bug categorization process. See the following page for details: http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines#Priority_and_Target_Milestone If you feel the updated priority is incorrect, please send an email to eclipselink-users@eclipse.org.
>Results: on JBoss 6.0.0 M1 - JPA 2.0 XSD ok, JPA 2.0 API ok >Pending: 1) verify that shared-cache-mode>NONE</shared-cache-mode> - actually works and does not just pass validation or relaxed validation - thanks Peter 2) dynamic weaving (instrumentation) - (need to disable the tempClassLoader) - thanks Doug - see bug 252965 See continuing discussion on the EclipseLink users newsgroup post bug 302449 http://dev.eclipse.org/mhonarc/lists/eclipselink-users/msg04116.html >We need to reprioritize this enhancement request now that JBoss 6 is out >post the ear containing the latest example tutorial >update the wiki
>preparing EAR and SVN (EAR,EJB,WAR) tutorial projects for checkin >Wiki retrofit from JBoss 4.2.2 to JBoss 6.0.0M1 in progress
Created attachment 159113 [details] JBoss 5.1.0 or JBoss 6.0.0M1 JPA enterprise app Note: remove DDL generation in persistence.xml after the first deployment Note: The JPA 2.0 API will run on JBoss 6.0.0M1 (remove the entityManager.getMetamodel() call and revert the 2.0 XSD schema numbers to 1.0 in persistence.xml (and remove the JPA 2.0 schema test tag shared-cache-mode NONE) - see the EAR attached to bug 302449 for a one with JPA 2.0 functionality removed (so we can run on JBoss 5.1.0)
Created attachment 159114 [details] JPA 2.0 EAR application for JBoss 6.0.0M1
Created attachment 159115 [details] JPA 1.0 EAR application for JBoss 5.1.0
>See SVN rev# 6608 http://fisheye2.atlassian.com/changelog/eclipselink/?cs=6608 The demo will run out of the box with the DefaultDS HQSL datasource provided you have copied eclipselink.jar to the \common\lib directory.
>wiki content is being updated to JBoss 6.0.0 M1 configuration status http://wiki.eclipse.org/EclipseLink/Examples/JPA/JBoss_Web_Tutorial
>We need to answer the 2 questions in following user post from 20110303 http://community.jboss.org/message/590837?tstart=0
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
