Jump to: navigation, search

EclipseLink/UserGuide/MOXy/Type Level/Mapping to a Type or Element/Default Root Element

EclipseLink MOXy

Mailing ListForumsIRCmattermost
OpenHelp WantedBug Day
Browse Source

Elug api package icon.png Key API

Default Root Element

At least one of your mapped classes must have a default root element defined. This tells EclipseLink what the top-level root of your XML document will be. Consider the Customer and Address classes shown in this example:


These classes correspond to the XML schema, shown in this example.

<xsd:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
   <xsd:complexType name="address-type">
         <element name="street" type="xsd:string"/>
         <element name="city" type="xsd:string"/>
   <xsd:element name="customer" type="customer-type"/>
   <xsd:complexType name="customer-type">
         <xsd:element name="name" type="xsd:string"/>
         <xsd:element name="billing-address" type="address-type"/>
         <xsd:element name="shipping-address" type="address-type"/>

When an instance of the Customer class is persisted to XML, the EclipseLink runtime performs the following:

  1. Gets the default root element.The Customer class instance corresponds to the root of the XML document. The EclipseLink runtime uses the default root element specified on the descriptor (customer) to start the XML document. EclipseLink then uses the mappings on the descriptor to marshal the object's attributes:
  2. When the EclipseLink runtime encounters an object attribute such as billingAddress, it checks the mapping associated with it to determine with what element (billing-address) to continue:

    The EclipseLink runtime checks the mapping's reference descriptor (Address) to determine what attributes to persist:


Elug note icon.png

Note: The undefined document root element of a referenced object is ignored during marshalling with an any collection mapping and object mapping.

Version: 2.2.0
Other versions...