Difference between revisions of "EclipseLink/Examples/MOXy/NativeOxmJaxbContext"

From Eclipsepedia

Jump to: navigation, search
m (Map Your Objects using EclipseLink's Native OXM)
m (linked to elug)
Line 5: Line 5:
  
 
== Create a sessions.xml File ==
 
== Create a sessions.xml File ==
Create a sessions.xml file.  There are two vital pieces of information to captureThe first is the name of the session, this name must correspond to the context path you wish to use when creating the JAXBContent. The second is the location of your mapping metadata.
+
Create a sessions.xml file.  There are two vital pieces of information to capture:
 +
*The name of the session -- This name must correspond to the context path you wish to use when creating the JAXBContent.
 +
*The location of your mapping metadata.
 +
 
 +
 
 +
See [[Creating a Session (ELUG)]] in the ''[[EclipseLink/UserGuide|EclipseLink User's Guide]]'' for complete information.
  
 
== Create the JAXBContext ==
 
== Create the JAXBContext ==

Revision as of 14:00, 31 January 2008

Map Your Objects using EclipseLink's Native OXM

EclipseLink offers meet-in-the-middle object-to-XML mapping. This allows you to map an existing Java objects to an existing XML schema. This can be done programmatically or visually using our mapping editor.

See Configuring an XML Mapping (ELUG) in the EclipseLink User's Guide for complete information.

Create a sessions.xml File

Create a sessions.xml file. There are two vital pieces of information to capture:

  • The name of the session -- This name must correspond to the context path you wish to use when creating the JAXBContent.
  • The location of your mapping metadata.


See Creating a Session (ELUG) in the EclipseLink User's Guide for complete information.

Create the JAXBContext

Create the JAXBContext using the context path option:

Code Example
JAXBContext.newInstance("com.example.model");