tag:blogger.com,1999:blog-13556721.post5382206389908842196..comments2023-05-29T18:53:18.727+09:30Comments on The Buttso Blathers: Plugging in a later version of EclipseLink to WebLogic ServerButtsohttp://www.blogger.com/profile/03968454565733104381noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-13556721.post-40926264071156769332015-01-21T17:47:00.599+10:302015-01-21T17:47:00.599+10:30>so weblogic ships jpa 2.1 jar in 12.1.2 but we...>so weblogic ships jpa 2.1 jar in 12.1.2 but we cannot use it? really?<br /><br />WebLogic Server 12.1.2 doesn't provide support for JPA 2.1.<br /><br />WebLogic Server 12.1.3 does provide support for JPA 2.1.<br /><br />I'd recommend if you want to use JPA 2.1 you use WebLogic Server 12.1.3.<br />Buttsohttps://www.blogger.com/profile/03968454565733104381noreply@blogger.comtag:blogger.com,1999:blog-13556721.post-12316118879316242722015-01-21T06:43:14.495+10:302015-01-21T06:43:14.495+10:30so weblogic ships jpa 2.1 jar in 12.1.2 but we can...so weblogic ships jpa 2.1 jar in 12.1.2 but we cannot use it? really?Kalpesh Sonihttps://www.blogger.com/profile/16188622811832015268noreply@blogger.comtag:blogger.com,1999:blog-13556721.post-90176908821958235292014-04-09T10:11:58.997+09:302014-04-09T10:11:58.997+09:30WLS 12.1.2 supports JPA 2.0.
Updating to JPA 2....WLS 12.1.2 supports JPA 2.0. <br /><br />Updating to JPA 2.1 on WLS 12.1.2 is not really possible to do as there are some integration points within the container to allow it to work properly and these are currently based on the mandated JPA 2.0 specification.<br /><br />The good news is that we will be supporting an optional update to JPA 2.1 in the forthcoming WLS 12.1.3 release, so the steps you have shown here will be possible to perform and have the container support JPA 2.1 instead of the default JPA 2.0 it is configured with. <br />Buttsohttps://www.blogger.com/profile/03968454565733104381noreply@blogger.comtag:blogger.com,1999:blog-13556721.post-34056304977590896892014-04-01T02:19:39.008+10:302014-04-01T02:19:39.008+10:30I am trying to upgrade my weblogic JPA (eclipselin...I am trying to upgrade my weblogic JPA (eclipselink) version to 2.1?<br /><br />Hi,<br /> <br />how to enable JPA2.1 support in weblogic 12.1.2 ?<br /> <br />I am finding javax.persistence_2.1.0.0_1-0-2.jar in /modules/ directory of my weblogic 12.1.2 production installation. but I am not able use JPA2.1 methods , during runtime , I am getting noSuchMethod error when I try to call createStoredProcedureQuery. but in the javax.persistence_2.1.0.0_1-0-2.jar it is there.<br /> <br />StoredProcedureQuery storedProcedure =<br />entityManager.createStoredProcedureQuery("SP_GET_GSA_CAMEL2");<br /> <br /> <br />I have added the below line in commEnv.sh, But no help. Still getting the error.<br /> <br />export PRE_CLASSPATH=/wls/product/ofm12.1.2/oracle_common/modules/javax.persistence_2.1.0.0_1-0-2.jar:<br /> <br />can somebody reply any specific steps I have to follow to enable JPA2.1 features in weblogic 12.1.2.<br /> <br />regards<br />MuthuvelAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-13556721.post-43682355649820492232014-01-30T15:14:08.742+10:302014-01-30T15:14:08.742+10:30Had this problem recently, and this article helped...Had this problem recently, and this article helped resolve it.Anonymoushttps://www.blogger.com/profile/00869496028596976417noreply@blogger.comtag:blogger.com,1999:blog-13556721.post-85596240676439640652011-10-06T09:17:23.833+10:302011-10-06T09:17:23.833+10:30Hi --
The primary difference here that you need ...Hi -- <br /><br />The primary difference here that you need to take into account is that Tomcat is a servlet container and doesn't provide any form of default JPA implementation.<br /><br />WebLogic Server on the other hand (and GlassFish and JBoss and TomEE now) are Java EE servers and therefore provide a default JPA implementation as part of their runtime. <br /><br />If you are deploying your application to WebLogic Server, then unless you have a specific need for a specific version of EclipseLink, you really don't need to bundle anything with the application. Since WebLogic Server provides the JPA API/implementation, your application doesn't need to provide.<br /><br />The EclipseLink 2.1.3 version output you see will be from the default version that WebLogic Server provides as part of it's Java EE requirements. <br /><br />If you want to change the version of EclipseLink that WebLogic Server uses to match what you are needing to bundle inside your application to support JPA on Tomcat, then you'll need to follow the sorts of instructions here.<br /><br />You may perhaps see that as "make work" you have to do in order to get WebLogic Server to use your app to deploy -- I'd see it a little differently in that you are needing to do more work in your application running on Tomcat (ie transaction management, library bundling) since it doesn't provide JPA support. <br /><br />Hope that helps some.<br /><br />-steve-Buttsohttps://www.blogger.com/profile/03968454565733104381noreply@blogger.comtag:blogger.com,1999:blog-13556721.post-73482677908409879082011-10-05T23:04:54.356+10:302011-10-05T23:04:54.356+10:30First comment: why isn't simply putting the 2....First comment: why isn't simply putting the 2.x eclipselink.jar in the webapp's WEB-INF/lib folder an option? Then the configuration wouldn't be required right?<br /><br><br />I need to deploy a J2EE container agnostic webapp, and it currently works under tomcat/eclipselink 2.1.1/MySQL. Deploying the same webapp in WebLogic 10.3.5 results in this sent to the console when the EntityManager connects:<br /><br><br /><br><br />INFO: EclipseLink, version: Eclipse Persistence Services - 2.1.3.v20110304-r9073<br /><br><br />Oct 5, 2011 7:53:36 AM org.eclipse.persistence.session.file:/C:/Oracle/Middleware/user_projects/domains/titn/autodeploy/titn/WEB-INF/classes/_titn<br /><br><br /><br><br />The exact same log statement when running under tomcat produces the expected version: 2.1.1.v20100817-r8050<br /><br><br />It's driving me insane. I have no idea where it's getting 2.1.3 from, and then when it tries the first insert, I get a constraint violation saying the PK is null when commit() is called!<br /><br><br />Do you have any diagnostic suggestions or form recommendations?Anonymousnoreply@blogger.com