This content has been marked as final. Show 3 replies
My page quoted above is mostly for older versions of WebLogic 10.3.3.0 and below that could not handle container managed JPA 2.0 injection. For WebLogic 10.3.5.0 and 10.3.4.0 JPA 2.0 is fully functional but will need to be enabled (the best way is to install OEPE, create a server profile to your WebLogic 10.3.4/10.3.4 instance - and select the "Java Persistence 2.0 - Install" link on the dialog in the Eclipse IDE). However, Kodo (based on OpenJPA) is not actively developed. I would switch to EclipseLink which is the Java EE 6 reference implementation. You can do this by changing the default persistence provider in the console from Kodo to TopLink (wraps EclipseLink) or specifying the provider in your persistence.xml.
The link you quote is the section for WebLogic 10.3.3.0
What you need is the new section I wrote in Jan 2011 for the 10.3.4.0
See my tutorials for details - where you can also see the source.
There are other way to enabled jap2.0(kodo/openjpa) ,but OEPE excepted ?
the page you quote I had readi it , but it does not work.
I wish I could change it to Eclipselink, but my cto don't agree that.
I'm sorry my bokenEnglish, thanks for your answer.
by the way,
it seems the behavior that the method "merge()" of entityManage in openjpa is different from in eclipselink.
merge of openjpa would ignored null value, but not eclipselink.