Jump to: navigation, search

Difference between revisions of "EclipseLink/FAQ/SDO"

Line 1: Line 1:
 
The Service Data Object (SDO) service allows developers to generate dynamic and static SDO models from an XSD and use these within their application. In addition to the XML binding capabilities defined in the specification additional flexibility is provided by the Object-XML service. This approach provides a solution for applications requiring less coupling to the data structures being accessed and modified. Support for wrapping a Java object (i.e. JPA entity) within a DataObject will be provided to enable the usage of existing domain models with SDO.
 
The Service Data Object (SDO) service allows developers to generate dynamic and static SDO models from an XSD and use these within their application. In addition to the XML binding capabilities defined in the specification additional flexibility is provided by the Object-XML service. This approach provides a solution for applications requiring less coupling to the data structures being accessed and modified. Support for wrapping a Java object (i.e. JPA entity) within a DataObject will be provided to enable the usage of existing domain models with SDO.
  
[[Category:EclipseLink FAQ]]
+
[[Category:EclipseLink FAQ|SDO]]

Revision as of 10:49, 7 January 2008

The Service Data Object (SDO) service allows developers to generate dynamic and static SDO models from an XSD and use these within their application. In addition to the XML binding capabilities defined in the specification additional flexibility is provided by the Object-XML service. This approach provides a solution for applications requiring less coupling to the data structures being accessed and modified. Support for wrapping a Java object (i.e. JPA entity) within a DataObject will be provided to enable the usage of existing domain models with SDO.