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
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.

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 Sutherland
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
(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 James
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/
Re: (no subject) [message #702719 is a reply to message #701913] Tue, 26 July 2011 18:08 Go to previous message
Kamal  is currently offline Kamal
Messages: 9
Registered: May 2011
Junior Member
Just what I wanted to hear. Thank you for the clear and precise answer James.
Previous Topic:Installation of EclipseLink with Tomcat 7
Next Topic:Invalid column name problem
Goto Forum:
  


Current Time: Wed Sep 17 15:44:37 GMT 2014

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

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