Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Talk:EclipseLink/DesignDocs/384399
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 in this way.
- James.sutherland.oracle.com 17:20, 27 August 2012 (UTC)
---
Refer to my example in Concepts section as to how binary compatibility could be maintained for the ORM piece
- http://wiki.eclipse.org/EclipseLink/DesignDocs/384399#Generics_.26_Parameterized_Types
- blaise.doughan.oracle.com 18:52, 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)
NoSQL
I assume this project would also include moving the NoSQL/EIS class into the nosql component. Note that nosql would most likely need to depend on both jpa and jaxb components.
- James.sutherland.oracle.com 17:23, 27 August 2012 (UTC)