| Re: [eclipselink-dev] Eclipselink 2 / JPA 2 with WebLogic 10.3.3 |
Michael, Sounds familiar – you are getting the same CNFE during EMF preprocessing as Jehanzeb from March 2010. http://dev.eclipse.org/mhonarc/lists/eclipselink-users/msg04375.html Note: JPA 2.0 (JSR-317) is part of the Java EE 6 specification and started officially shipping with WebLogic 10.3.4.0 in Jan 2011. It looks from your stacktrace that you are using CDI in the EJB container in I assume a SSB – also using the JRockit or the SUN JVM may make a difference as I would have expected you to fail later on a JPA 2 internal call like getMetamodel() or a NSME on getValidationMode(). Therefore if you wish to use @PersistenceContext injection – for JPA 2.0 – this is only possible in WebLogic 10.3.4.0 or later as the DI infrastructure is not in 10.3.3.0. See the comment on my investigation bug for JPA 2.0 on WebLogic 10.3.3 below. https://bugs.eclipse.org/bugs/show_bug.cgi?id=296271#c11 The workaround is to use an application managed @PersistenceUnit and the filtering classloader until you are able to upgrade to 10.3.4.0 - this would be available in the WAR not the EJB.jar. I may not have all the details on enabling JPA 2.0 in WebLogic 10.3.3.0 fresh anymore. Is there any way for you to upgrade to a later WebLogic version. There may be an even hacky way to do this. Take the QWG8 patch for 10.3.4 and apply it to 10.3.3 – entirely experimental since my documentation on 10.3.3.0 was written before 10.3.4 was out – but it may work – but at this point the jar may not even work with the older version of WebLogic – and you may as well go all the way and download 10.3.5.0 – see the 12c download below http://www.oracle.com/technetwork/middleware/fusion-middleware/downloads/index.html Have you tried my PRE_CLASSPATH workaround to put the javax.persistence library higher in the classpath in comEnv.cmd – a hack for the server – but required in yourcase if you want to get JPA 2.0 working on a version of WebLogic developed before the spec was released. http://wiki.eclipse.org/EclipseLink/Development/JPA_2.0/weblogic#Enabling_JPA2_support I quote….
C:\opt\wls10340_pub110115\wlserver_10.3\common\bin\commEnv.cmd set PRE_CLASSPATH=%BEA_HOME%\modules\javax.persistence_1.0.0.0_2-0-0.jar;%BEA_HOME%\modules\com.oracle.jpa2support_1.0.0.0_2-0.jar / Michael O’Brien From: Michael Gitelman [mailto:mgitelman@xxxxxxxxxxxxxxx] Michael, Thank you very much for your help. I believe I have followed your instructions for DI1.1. I am getting the following error during EAR Deployment:
Best regards, Michael Gitelman Delphi Technology, Inc. One Washington Mall, Suite 3 Boston, MA 02108 O: 617 259 1256 F: 617 778 2296 Experience, Innovation... Results. From: Michael O'Brien [mailto:Michael.F.Obrien@xxxxxxxxx] Michael, Hi, there is a section linked from http://wiki.eclipse.org/EclipseLink/Examples/JPA/WebLogic_Web_Tutorial#JSR-317_JPA_2.0_Support to that covers 10.3.3 – primarily through the <prefer-application-packages> classloader order workaround. The WebLogic Server 10.3.4.0/10.3.5.0 release deprecates these instructions. If you read through the page above you will see that injection of a full container managed JPA 2.0 @PersistenceContext entityManager may have issues in the past (JPA 1.0 injection is fine) – until 10.3.4.0 – where the AOP injection framework in WebLogic was updated to work with the 2.0 providers. Regardless, you are able to use the JPA 2.0 API at runtime however even if you use a 1.0 schema. Currently even in 10.3.5 JPA 1.0 is still enabled by default – there are several ways enable JPA 2.0 – one way of which is via the OEPE plugin for Eclipse at design time. After you enable JPA 2.0 – full JPA 2.0 injection in the EJB container is possible. I am posting to the EclipseLink Users newsgroup to widen the audience and responses. If you follow the 7 instructions in design issue 1.1 Alternative 3 above – you will have one possible workaround for the 10.3.3 specific issue What problems are you seeing? Are you having runtime issues with @PersistenceContext CDI injection or using the 2.0 schema in your XSD during deployment? Thank you /Michael O’Brien From: Michael Gitelman Date: Tue, 7 Feb 2012 13:22:36 -0500 To: michael.f.obrien eclipselink org Subject: Eclipselink 2 / JPA 2 with WebLogic 10.3.3 Hi Michael, I read your tutorial on EclipseLink /Development / JPA 2.0 / Weblogic. Unfortunately, I couldn’t find the information on how it works with WL 10.3.3. Unfortunately, I am stuck with that release for another year and need to make it work with JPA 2 / Eclipselink 2.2. However, everywhere I look I find references for 10.3.3 instructions but not the instructions themselves. Could you help me out to find a document specific to 10.3.3? Best regards, Michael Gitelman |