Jump to: navigation, search

Difference between revisions of "EclipseLink/Examples/MOXy"

(EclipseLink JAXB Examples)
(EclipseLink JAXB Examples)
Line 13: Line 13:
 
* [[EclipseLink/Examples/MOXy/GettingStarted | Getting Started]]
 
* [[EclipseLink/Examples/MOXy/GettingStarted | Getting Started]]
 
*: No metadata is required to convert your existing object model to XML.  Supply metadata (using annotations or XML) only when you need to fine tune the XML representation.  Get started using MOXy.
 
*: No metadata is required to convert your existing object model to XML.  Supply metadata (using annotations or XML) only when you need to fine tune the XML representation.  Get started using MOXy.
* [[EclipseLink/Examples/MOXy/JAXB | Using EclipseLink JAXB to Manipulate XML]]
+
* [[EclipseLink/Examples/MOXy/JAXB | Using EclipseLink JAXB]]
** [[EclipseLink/Examples/MOXy/JAXB#Running_the_JAXB_Compiler | Running the JAXB Compiler - Generating classes and mappings from XSD]]
+
*: Java Architecture for XML Binding (JSR 222) is the standard for XML Binding in Java. JAXB covers 100% of XML Schema concepts. Learn how to use MOXy as your JAXB provider.
** [[EclipseLink/Examples/MOXy/JAXB#Creating_a_JAXBContext_using_jaxb.properties | Creating an EclipseLink MOXy JAXBContext]]
+
** [[EclipseLink/Examples/MOXy/JAXB#Unmarshalling_the_XML_Document | Unmarshalling an XML Document]]
+
** [[EclipseLink/Examples/MOXy/JAXB#Marshalling_the_Objects_to_XML | Marshalling objects into XML]]
+
** [[EclipseLink/Examples/MOXy/JAXB#Using_JAXBContext_to_Generate_an_XML_Schema | Generating an XSD using a JAXBContext]]
+
 
* [[EclipseLink/Examples/MOXy/MeetInTheMiddle | Meet in the Middle Mapping]]
 
* [[EclipseLink/Examples/MOXy/MeetInTheMiddle | Meet in the Middle Mapping]]
 
*: Normally in XML Binding solutions there is a one-to-one correspondence between the object model and the levels of nesting in the resulting XML document.  Learn how to leverage MOXy’s XPath based mapping to remove these limitations.
 
*: Normally in XML Binding solutions there is a one-to-one correspondence between the object model and the levels of nesting in the resulting XML document.  Learn how to leverage MOXy’s XPath based mapping to remove these limitations.

Revision as of 16:31, 29 January 2010


The following examples are provided to assist developers with their adoption and usage of EclipseLink's JAXB and native OXM functionality.

JAXB Examples

EclipseLink provides standards based JAXB implementation with many extensions. These references are for the JAXB 2.0 reference implementation which is included within EclipseLink for its XSD compiler capabilities (XJC).

EclipseLink JAXB Examples

  • Getting Started
    No metadata is required to convert your existing object model to XML. Supply metadata (using annotations or XML) only when you need to fine tune the XML representation. Get started using MOXy.
  • Using EclipseLink JAXB
    Java Architecture for XML Binding (JSR 222) is the standard for XML Binding in Java. JAXB covers 100% of XML Schema concepts. Learn how to use MOXy as your JAXB provider.
  • Meet in the Middle Mapping
    Normally in XML Binding solutions there is a one-to-one correspondence between the object model and the levels of nesting in the resulting XML document. Learn how to leverage MOXy’s XPath based mapping to remove these limitations.
  • Mapping JPA Entities to XML
    JPA provides an easy and powerful means to use Java objects to interact with a relational database. These Java objects are called entities, and have their own characteristics. Some of these characteristics (bidirectional relationships, compound keys, embedded key classes, and lazy loading) can cause challenges when mapping these objects to XML. Learn how to easily map JPA entities to XML using MOXy.
  • Converting POJOs to/from SDO DataObjects using the POJO/SDO Bridge (via JAXB)
    Using SDO or SCA and want to leverage JPA to access your persistent data? Learn how to expose your objects through SDO using MOXy.

Using Native OXM through JAXB Examples