Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » EclipseLink » Toplink 10 to Eclipselink migration(Toplink 10 to Eclipselink migration without JPA)
Toplink 10 to Eclipselink migration [message #699990] Fri, 22 July 2011 16:58 Go to next message
Kamal is currently offline Kamal Friend
Messages: 9
Registered: May 2011
Junior Member
We are trying to port our Application from Toplink 10.1.3 to Eclipselink due to licensing issues. But we cannot go the JPA route as the application uses a custom framework for all it's mappings and it will be a big change to modify these. I could make most of the application work with replacing the Toplink jar with Eclipselink and using the migration tool.

I have the following questions though
1. Would it be possible to use newer features of Eclipselink without following the JPA approach? Does Eclipselink have documentation and support for the non JPA approach?

2. How long is Eclipselink planning to support backward compatibility for Toplink APIs? Would it be possible to upgrade to newer Eclipselink versions to keep up with newer Database releases etc but still keep references to Toplink APIs?

3. Can we use JPA and direct API access in the same project? The persistence objects needs to be in the same context.

Report message to a moderator

Re: Toplink 10 to Eclipselink migration [message #701872 is a reply to message #699990] Mon, 25 July 2011 17:40 Go to previous messageGo to next message
James Sutherland is currently offline James SutherlandFriend
Messages: 1939
Registered: July 2009
Location: Ottawa, Canada
Senior Member
1 - EclipseLink continues to fully support the "native API" (non JPA usage)

2 - No plans ever to remove it, the JPA support is built on top of the native EclipseLink API. Most new features are exposed in the native API (and wrapped by JPA), a few only make sense in the context of JPA (Criteria, JPA MetaModel).

3 - You can access the EclipseLink Session from a JPA EntityManager or EntityManagerFactory (and can construct an EntityManagerFactory from an EclipseLink Session). You can use both APIs together.

James : Wiki : Book : Blog : Twitter

Report message to a moderator

(no subject) [message #701913 is a reply to message #699990] Mon, 25 July 2011 17:40 Go to previous messageGo to next message
James is currently offline JamesFriend
Messages: 272
Registered: July 2009
Senior Member
1 - EclipseLink continues to fully support the "native API" (non JPA usage)

2 - No plans ever to remove it, the JPA support is built on top of the native EclipseLink API. Most new features are exposed in the native API (and wrapped by JPA), a few only make sense in the context of JPA (Criteria, JPA MetaModel).

3 - You can access the EclipseLink Session from a JPA EntityManager or EntityManagerFactory (and can construct an EntityManagerFactory from an EclipseLink Session). You can use both APIs together.


--
James : http://wiki.eclipse.org/EclipseLink : http://en.wikibooks.org/wiki/Java_Persistence : http://java-persistence-performance.blogspot.com/

Report message to a moderator

Re: (no subject) [message #702719 is a reply to message #701913] Tue, 26 July 2011 18:08 Go to previous messageGo to next message
Kamal is currently offline Kamal Friend
Messages: 9
Registered: May 2011
Junior Member
Just what I wanted to hear. Thank you for the clear and precise answer James.

Report message to a moderator

Re: Toplink 10 to Eclipselink migration [message #1854538 is a reply to message #701872] Wed, 24 August 2022 12:49 Go to previous message
Joe Satriani is currently offline Joe SatrianiFriend
Messages: 1
Registered: August 2022
Junior Member
Hello James and Kamal (and anyone who can help),
this topic interests me as I'm trying to migrate a J2EE heavy application (jnlp) from Oracle OC4j (OAS) using Toplink, to RH JBoss using Eclipselink (without changing functional code of Beans).

If read-only java instructions are correctly translated in a SELECT SQL statement (example : ReadAllQuery query = new ReadAllQuery(Employee.class) ==> SELECT * FROM employee).

But, write java instructions seem not to be translated in corresponding SQL statements (example : session.acquireUnitOfWork().deleteObject(employeeSmith) ==> DELETE employee).

Is there any setup in JBoss or parameter for Eclipselink to activate this "translation" when EJB commits its transaction (as it was with Toplink) ?

Thanks in advance for your help and advices.

Regards

Report message to a moderator

Previous Topic:XA data source connection in EclipseLink in SpringBoot application.
Next Topic:Split module conflict between eclipse and jakarta.jakartaee.api
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Sat Nov 09 02:08:25 GMT 2024

Powered by FUDForum. Page generated in 0.03899 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly