Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » EclipseLink » Native ORM vs JPA(Is Native ORM Obsolete API)
Native ORM vs JPA [message #780786] Thu, 19 January 2012 06:26 Go to next message
Mohammad Abdo is currently offline Mohammad Abdo
Messages: 6
Registered: January 2012
Location: Jordan
Junior Member
Dears,

We already developed many Products using TopLink/EclipseLink Native ORM.

My Question is:
- Is Native ORM will have continuous development and support in future?
Or, Native ORM now considered obsolete approach and we have to plan migrating
our Proudcts from Native ORM to JPA?

Re: Native ORM vs JPA [message #780840 is a reply to message #780786] Thu, 19 January 2012 10:04 Go to previous messageGo to next message
James Sutherland is currently offline James Sutherland
Messages: 1939
Registered: July 2009
Location: Ottawa, Canada
Senior Member

JPA is the recommend API, a standard, and the target for any of our new development.

The native API is still fully supported. JPA is built on top of the native API, so most new JPA features are exposed through the native API.

You don't need to migrate, but you may want to, to bring your applications up to current standards and technology.


James : Wiki : Book : Blog : Twitter
Re: Native ORM vs JPA [message #781001 is a reply to message #780786] Thu, 19 January 2012 10:05 Go to previous message
James Sutherland is currently offline James Sutherland
Messages: 1939
Registered: July 2009
Location: Ottawa, Canada
Senior Member

JPA is the recommend API, a standard, and the target for any of our new development.

The native API is still fully supported. JPA is built on top of the native API, so most new JPA features are exposed through the native API.

You don't need to migrate, but you may want to, to bring your applications up to current standards and technology.

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


James : Wiki : Book : Blog : Twitter
Re: Native ORM vs JPA [message #781018 is a reply to message #780786] Thu, 19 January 2012 10:05 Go to previous message
James Sutherland is currently offline James Sutherland
Messages: 1939
Registered: July 2009
Location: Ottawa, Canada
Senior Member

JPA is the recommend API, a standard, and the target for any of our new development.

The native API is still fully supported. JPA is built on top of the native API, so most new JPA features are exposed through the native API.

You don't need to migrate, but you may want to, to bring your applications up to current standards and technology.

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


James : Wiki : Book : Blog : Twitter
Re: Native ORM vs JPA [message #781035 is a reply to message #780786] Thu, 19 January 2012 10:05 Go to previous message
James Sutherland is currently offline James Sutherland
Messages: 1939
Registered: July 2009
Location: Ottawa, Canada
Senior Member

JPA is the recommend API, a standard, and the target for any of our new development.

The native API is still fully supported. JPA is built on top of the native API, so most new JPA features are exposed through the native API.

You don't need to migrate, but you may want to, to bring your applications up to current standards and technology.

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


James : Wiki : Book : Blog : Twitter
Previous Topic:show parameter values in sql log (no JPA)
Next Topic:Transaction logging
Goto Forum:
  


Current Time: Wed Aug 20 10:45:12 EDT 2014

Powered by FUDForum. Page generated in 0.01720 seconds