|Toplink 10 to Eclipselink migration [message #699990]
||Fri, 22 July 2011 12:58
Registered: May 2011
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.
Powered by FUDForum
. Page generated in 0.01711 seconds