| Re: [eclipselink-users] Eclipselink 2 / JPA 2 with WebLogic 10.3.3 |
Michael, Hi, your configuration closely matches my example for WebLogic 10.3.4 that uses remote session beans (I previously also prototyped on GlassFish 3 using the beta of NetBeans 6.9 – before 10.3.4 came out). From a quick inspection – it looks fine, your use of injection and configuration is standard EE http://wiki.eclipse.org/EclipseLink/Examples/Distributed The source and details of this example that uses old school EJB 3.0 distributed session beans to hammer the WebLogic server’s persistence units instead of a more Java EE 6 JAX-RS approach are available on the wiki and SVN source links. In answer to your question about 10.3.4/10.3.5 and JPA 2.0 – I can assure you that everything is fully functional – I even upgrade the JPA implementation to the latest EclipseLink 2.3 in the modules directory. The WebLogic 10.3.5.0/JPA2/JSF2/JAX-RS 1.1 combination is the basis of all my full Java EE 6 tutorials and presentations for a complete ORM/OXM stack. I use WebLogic 10.3.5.0 both at work and at home for all my production EAR deployments. I recommend you download the 10.3.5.0 version that comes with the Oracle Enterprise Pack for Eclipse and prototype your app in parallel there. I am currently out of the office today and will look at the details of your 10.3.3 exceptions when I return later tomorrow. I am posting to the newsgroup until tomorrow. I will at that time look up my saved EAR’s for 10.3.3.0 if I did anything different – I have several examples of an application managed persistence unit – but not in source control that I will share. Until then go through the JPA 2.0 on WebLogic 10.3.3.0 investigation bug http://bugs.eclipse.org/296271 You will want to use the 3rd EAR attachment – minus a compatible version of the full 5Mb eclipselink.jar form 2009 Alternative #3 EAR (add 5mb eclipselink jar beside jpa2 spec jar before deployment) (101.77 KB, application/x-zip-compressed) 2009-12-03 23:34 EST, Michael OBrien no flags Details Essentially, you do everything in a servlet on the war and change from JTA to RESOURCE_LOCAL, and don’t require a db connection on the server – you move the config to persistence.xml (see the Tomcat tutorial for a web deployment scenario) Note: use of the filtering classloader only works with non-JTA persistence contexts where the EJB’s classloader is overridden by the libraries you ship with your EAR. My 10.3.5.0 weblogic-application.xml namespaces are different <wls:weblogic-application xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-application" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/javaee_5.xsd http://xmlns.oracle.com/weblogic/weblogic-application http://xmlns.oracle.com/weblogic/weblogic-application/1.2/weblogic-application.xsd"> From 10.3.3.0 <wls:weblogic-application xmlns:wls="http://www.bea.com/ns/weblogic/weblogic-application" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/javaee_5.xsd http://www.bea.com/ns/weblogic/weblogic-application http://www.bea.com/ns/weblogic/weblogic-application/1.0/weblogic-application.xsd"> Thank you / Michael O’Brien From: Michael Gitelman [mailto:mgitelman@xxxxxxxxxxxxxxx] Hi Michael, Thank you very much for your help. I am developing a new JSF 2 / JPA 2 module for the existing suite of our product that runs on 10.3.3 in a few dozen of customer environments. My module needs to be deployed in the summer while we are planning to migrate them to 10.3.4 (or possibly to 10.3.5, if I can convince them that 10.3.5 works well with JSF 2 / JPA 2 ) in 2013. I developed a prototype in NetBeans 6.9 and deployed it on the GlassFish 3.0.1 and it worked perfectly fine. When I migrated to WL 10.3.3 my problems began. You correctly figured out what I am doing: 1. I did try the hacky approach by getting the jars for 10.3.4 and pre-pending them to the classpath:
2. My weblogic-application.xml looks like that:
3. My persistence unit looks like that (I changed the version from “2.0” to “1.0” to make it work):
4. I have a session bean that looks like the following:
I had to create a local interface to make it work on WL 10.3.3 (in GlassFish I simply used @LocalBean). 5. With the above configuration I get the following error when I deploy the application:
Before I added javax.persistence_1.0.0.0_2-0-0.jar and com.oracle.jpa2support_1.0.0.0_2-0.jar to the classpath I would get a null pointer in the highlighted line above: Query query = em.createNamedQuery("ConfigEventHeader.findAll"); 6. When I try to re-deploy I get the following:
I would like to figure out if I can the above approach. If that wouldn’t work, I would like to try application managed @PersistenceUnit and the filtering classloader. However, I wasn’t able to find the instructions for the latter. Your help and suggestions are greatly appreciated. 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, 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…. § manually add the com.oracle.jpa2support_1.0.0.0_2-0.jar ahead of the server classpath by following the instructions in the documentation at § http://download.oracle.com/docs/cd/E17904_01/web.1111/e13720/using_toplink.htm#EJBAD1309 § or do it manually by modifying the following line directly on your server 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 |