| Native Eclipselink versus JPA Eclipselink defaults [message #1090731] |
Tue, 20 August 2013 15:06 |
 Roger Spall
Messages: 17
Registered: January 2013 |
Junior Member |
|
|
Clearly native (good old Mapping Workbench, ReadAllQueries, etc) and JPA Eclipselink use the same 'core code'. In essence (and an over simplification), it appears that Native and JPA Eclipselink use similar design concepts, however the JPA spec is imposed by the Java J2EE community whereas Native was controlled by Oracle.
Anyway, I am continuing to convert a large project from Native to JPA Eclipselink and learning (the hard way) about how some of these defaults vary, e.g. the default cascade rules for Native versus JPA, or the default flushing of Auto for JPA and Commit for Native (which causes update flushing to occur early in JPA when a related Object Query is run).
Anyway, is there a document anywhere which summarizes the key differences (e.g. defaults for various options) between JPA and Native Eclipselink?
|
|
|
Powered by
FUDForum. Page generated in 0.03065 seconds
] 
Search
Help
Register
Login
Home
