Skip to main content
Jump to: navigation, search

Talk:EclipseLink/DesignDocs/384399

Revision as of 13:20, 27 August 2012 by James.sutherland.oracle.com (Talk | contribs) (New page: ===Binary Compatibility / Backward Compatibility=== I'm not sure the changes can be backward compatible or binary compatible. I think the usage of generics might be able to resolve many of...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Binary Compatibility / Backward Compatibility

I'm not sure the changes can be backward compatible or binary compatible. I think the usage of generics might be able to resolve many of the backward compatibility issues, but this would require a recompile, I'm not sure if generics are binary compatible.

James.sutherland.oracle.com 17:20, 27 August 2012 (UTC)

ORM Deployment XML

I don't think we can remove this. It is still our only meta-data format for many of our API's (native ORM, DBWS, BPEL) and has not been deprecated or even replaceable without requiring a migration to JPA. Potentially we could deprecated it and provide a way to use the JPA orm.xml meta-data format for native ORM (DBWS, BPEL), and provide some migration utilities perhaps. But would probably require a couple releases to get rid of it.

Note, getting rid, or deprecating the project deployment XML would also mean deprecating or removing the Mapping Workbench and JDev/ADF native ORM support, or migrating these to generate a JPA orm.xml file.

James.sutherland.oracle.com 17:20, 27 August 2012 (UTC)

Back to the top