This content has been marked as final. Show 16 replies
JPA2.0 implementation on Weblogic can be expected with next PatchSet (PS2)Sorry, I need to correct this statement -- Oracle will not be adding JPA 2.0 support to WebLogic Server 11g R1 in the next scheduled patchset (PS2) as stated above.
In PS2 we have incorporated TopLink (11g R1) as a fully integrated JPA provider with WebLogic Server, in addition to the existing Kodo/OpenJPA support we have. This allows TopLink to be configured and used as the default JPA provider for a given domain, if desired.
WebLogic Server will provide support for EJB 3.1/JPA 2.0 in a future release that is currently under development, but not with PS2.
WLS Product Management
In PS2 we have incorporated TopLink (11g R1) as a fully integrated JPA provider with WebLogic ServerWhich version of TopLink/EclipseLink has been integrated ?
in addition to the existing Kodo/OpenJPA support we haveWhich one do you advise to use: TopLink/EclipseLink, Kodo or OpenJPA ?
Edited by: user12219863 on Feb 23, 2010 5:34 AM
WLS 11g R1 PS2 (10.3.3) has been released and is now available on OTN.
There are a couple of changes to be aware of relating to this topic:
1. We have updated the version of EclipseLink to 2.0.2 in this release. We still expose only the JPA 1.0 API via WLS, so WLS 11g R1 PS still only supports JPA 1.0 despite EclipseLink 2.0 being JPA 2.0 compatible. There are a few things you can do from an application managed context to exercise EclipseLink 2.0 features, but as far as JPA goes, WLS 11g R1 PS2 still is JPA 1.0 only. We are moving quite carefully here so as to not cause any disruptions to existing deployed applications using JPA 1.0. We plan to provide full JPA 2.0 support in a future patchset.
2. We have integrated EclipseLink more fully with WLS in this release. Now you can specify a default JPA provider (via a JPAMBean) at the domain level, enabling you to switch the default from Kodo/OpenJPA to EclipseLink if you wish. This means that if no <provider> class is specified in persistence.xml, the setting from the domain level will be applied.
3. We have also integrated EclipseLink logging into WLS so you can set respective log levels for EclipseLink, or the existing WLS JPA categories, and the messages will be captured in the WLS logging system.'
We would advise you to use EclipseLink as that is our stated strategic direction for JPA.
gday Brian --
I am somewhat restricted in what I can say publicly.
But let me try work through some thoughts.
1. We have the actual JPA 2.0 implementation via EclipseLink 2.0.2 in WLS PS2, so that element of the work in already in place and released.
2. The next step will be to expose the JPA 2.0 API on WLS. We have tested this thoroughly on the WLS version we are working that follows PS2 and are confident that we can make the change with no impact to existing JPA 1.0 applications.
3. PS2 has just been released to OTN, say what you might call beginning of May.
4. The next release vehicle will presumably be PS3.
5. The timeframe between PS1 (Nov 09) and PS2 (May 10) based on the public OTN postings of the software, was around 6 months.
The aboive is not a commitment to deliver JPA 2.0 nor is it the promise of any specific timeframe.
But if you thought along those lines, it'd probably give you something you may be able to use to ballpark a timeframe.
paata_lom wrote:Hi Paata -- we're very excited by what EJB 3.1 offers as well. We are working hard on the implementation, but unfortunately WLS 11g R1 PS2 doesn't support EJB 3.1. We will support it in a future release along with the other Java EE 6 specs we are working on.
Thank you very much for your helpful post.
does WLS 11g R1 PS2 (10.3.3) supports EJB 3.1 ?
EJB 3.1 has very good features : Singleton Beans, Schedulers, No Local Interface and so on....
I'll be greatly appreciated to see it into WLS.
In the meantime, if you are enthused by what Java EE 6 and EJB 3.1 in particular offers for developers, our new sibling GlassFish v3 provides a full Java EE 6 environment for you to start developing and running with. NetBeans 6.8 also has some nice support for the new Java EE 6 APIs that are well worth checking out.
I've billing system(EJB3) running on jboss as.
We're planning to move from jboss to WLS for some reasons.
There we have used ejb 3.0. In this version there is not singleton beans.
And for workaround we use JBoss EJB extensions - "Singleton MBeans".
Singleton Mbeans helped us so much, because we take 90% of DB (small Configuration tables) into memory which decrease serious round trips to database.
Now we want to migrate on WLS.
Is there anything like "Singleton Mbeans" ??
I think it will be more efficient and accurate to think about ejb 3.1(Singleton beans).
Yes we know that glassfish is fully supports java EE 6. We hadn't any problem into examples.
But we don't want to migrate from JBoss to glassfish and then to WLS.
We're waiting for you.
I'll be happy to see ejb 3.1 into WLS.