1 2 Previous Next 19 Replies Latest reply on Jan 19, 2011 5:22 PM by obrienmi8 Go to original post
      • 15. Re: Default JPA provider for Weblogic Server 10.3.2 (11g)
        Steve Button-Oracle
        I'm sure there will be restrictions on the architecture designs that can be constructed in some cases.

        But this is at least a step forward towards JPA 2.0 in PS2 with application managed JPA utilizing EclipseLink 2.0.

        The container managed support for JPA 2.0 will be in a subsequent patchset.

        If you take a look at the analysis on the EclipseLink website for using JPA 2.0 with WLS, you may see some other alternatives. These would not be supported, but may offer you some options if you want to explore yourself.


        Edited by: Steve Button on Apr 28, 2010 2:36 PM
        • 16. JPA app && JPA porlet form Weblogic Server 10.3.2 (11g) .

          i have a project JPA (hibernate provider) base that i can deploy in two formats:

          1) application
          2) portlet in a container porlet, for example liferay.

          if my project JPA is deployed like application my persistence.xml is read perfectly and my app works ok!
          if my project JPS is deployed like porlet my persistence is junked or bypassed and In the screen is appeared the next message:

          <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal user error> org.apache.openjpa.pers
          istence.ArgumentException: A JDBC Driver or DataSource class name must be specif
          ied in the ConnectionDriverName property.

          i understand that my persistence.xml isn´t reading!!

          In tomcat server runs like applications and porlet, i think that i have a problem when app runs in weblogic 10.3.2 + liferay 5.2.3 like porlet... because i´m sure that my persistence.xml is bypassed!!!!

          i need help! thanks guys!!!
          • 17. re: Default JPA provider for Weblogic Server 10.3.2 (11g)   .
            Steve Button-Oracle
            You may want to start a new thread for your Hibernate and Liferay issue.

            In this thread we were talking specifically about the JPA implementations that are provided with WLS.

            • 18. Re: Default JPA provider for Weblogic Server 10.3.2 (11g)
              For (EclipseLink 1.2) and (EclipseLink 2.0) the recommended approach is still option 3 - for a no-server-mod version.

              However, on this page are other options including container managed scenarios with their own issues that involve modifying the server classpath directly like...

              The page will be modified immediately after any subsequent version of WebLogic is out.

              See also the parent tutorial page for a standard EclipseLink JTA container managed EE (EJB/servlet) application on WebLogic

              thank you
              • 19. Re: Default JPA provider for Weblogic Server 10.3.2 (11g)
                See the recent OTN post from 20110115 detailing the latest release of Oracle WebLogic Server and some retesting of the previous issues related to JSR-317 JPA 2.0 support below.
                Re: Deploy Hibernate based EAR file on Weblogic 10.3.3?

                The latest release of Oracle WebLogic Server has been available on OTN at the following location since 20110115.

                This release provides support for JSR-317 JPA 2.0 container managed applications using the QWG8 patch or a manual prepending classpath change.

                In you were required to use the FilteringClassLoader via the *<wls:prefer-application-packages>* addition to your application managed persistence unit - this workaround as well as the persistence.xml renaming one is now fully deprecated and not required in for both application and container managed persistence contexts.
                As of 20110115 the 5 outstanding issues below look to be fixed by applying the http://download.oracle.com/docs/cd/E17904_01/web.1111/e13720/using_toplink.htm#EJBAD1309 patch for QWG8 or manually prepending to the WebLogic server classpath.
                commEnv.cmd: line 67
                @rem Set BEA Home
                set BEA_HOME=C:\opt\wls1034r20110115
                @rem Enable JPA 2.0 functionality on WebLogic Server 10.3.4 with the following patch line for commEnv.cmd:67
                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
                A JPA 2.0 EE application using EclipseLink as the JPA2 persistence provider on WebLogic is detailed in the analysis section below
                1) JPA 2.0 XSD parsing - verified
                2) New JPA 2.0 schema elements like <shared-cache-mode>NONE</shared-cache-mode> - verified
                3) JPA 2.0 runtime API like a entityManager.getMetamodel(); call on the Servlet or Stateless session bean - verified
                4) JPA 2.0 weaving/instrumentation - this will require a more detailed lazy model and more debugging to fully verify
                5) Dependency Injection of a container managed JPA 2.0 entityManager on a EJB component like a stateless session bean - verified
                OTN download
                Supported Oracle WebLogic Server Versions
                TopLink JPA 2.0 Specific documentation/patching
                EclipseLink Wiki: JPA 2.0 using EclipseLink on WebLogic analysis (XSD, Weaving, DI of @PersistenceContext)

                thank you
                /Michael O'Brien
                1 2 Previous Next