Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "EclipseLink/UserGuide/SDO/Introduction to EclipseLink SDO (ELUG)"

m (What You May Need to Know About Sequence, ChangeSummary, and DataGraph)
m
Line 55: Line 55:
  
  
[[Category:SDO]]
+
[[Category: EclipseLink User's Guide]]
 +
[[Category: Release 1.1]]
 +
[[Category: SDO]]

Revision as of 09:48, 23 April 2009

Information pending

This section introduces EclipseLink implementation of Service Data Objects (SDO) specification, as well as provides information on how you can use it in your application development.


Using SDO Metadata

SDO metadata is represented as Type and Property objects. You define the metadata at run time either programmatically, or from an XML schema.


Using Type

SDO Type acts similarly to a Class in Java, and provides much of the same metadata as the Java Reflection API provides for Java classes.

In EclipseLink, a Type wraps an object-XML mapping (OXM) descriptor.

Types can have supertypes, which corresponds to the EclipseLink concept of an inheritance policy (see ...).


What You May Need to Know About Open Sequenced Type

...

What You May Need to Know About DataObject Types for Data Types

...


Using Property

SDO property acts similarly to a property in Java and provides much of the same metadata as the Java Reflection API provides for Java fields or methods.

In EclipseLink, a Property wraps an object-XML mapping in the following way:


Defining Metadata

How to Use XSDHelper

How to Use TypeHelper

Using Data

Using DataObject (see 17.2.6 “Mapping converters and transformers” in JITDG/ELUG)

What You May Need to Know About Serialization in SDO (see 17.2.6.1 in JITDG/ELUG)

Using XMLDocument

What You May Need to Know About Sequence, ChangeSummary, and DataGraph

Back to the top