tag:blogger.com,1999:blog-7747481246630004369.post6627762530641966341..comments2022-03-02T22:07:49.417-05:00Comments on Java Persistence: Using JPA 2.0 in WebLogic 10.3.4Doughttp://www.blogger.com/profile/02383574560699818383noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7747481246630004369.post-72464659206237037942012-12-18T01:54:21.221-05:002012-12-18T01:54:21.221-05:00I recently fixed this problem on weblogic 10.3.3 w...I recently fixed this problem on weblogic 10.3.3 which is JPA1.0 complient I believe it will also work in your case have a look at below blog post<br /><br />http://javaiscoool.blogspot.com/2012/12/deploy-jpa20-application-on-weblogic1033.htmlsajjad parachahttps://www.blogger.com/profile/09656212868317790693noreply@blogger.comtag:blogger.com,1999:blog-7747481246630004369.post-20776699509688394182011-02-02T05:47:47.141-05:002011-02-02T05:47:47.141-05:00Interesting information. I was just talking to a o...Interesting information. I was just talking to a ops support guy for one client yesterday about server upgrade paths, and if they were to migrate today, from oc4j 10.1.3.4, it would most likely be to this version of WebLogic. The fact that with relatively little effort they could then enable JPA 2.0, and start slowly taking advantage of it, is something that I'll pass along. This particular fellow I mention already did some experimentation with key applications and WebLogic.ArvedShttps://www.blogger.com/profile/11208183111791675043noreply@blogger.com