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.
Difference between revisions of "EclipseLink/FAQ/MOXy"
< EclipseLink | FAQ
| Line 4: | Line 4: | ||
== How does EclipseLink MOXy differ from the JAXB reference implementation? == | == How does EclipseLink MOXy differ from the JAXB reference implementation? == | ||
| + | |||
| + | * EclipseLink MOXy provides support externalized mapping metadata. This means that plain old java objects can be mapped onto an XSD without requiring any annotations at all. | ||
| + | * EclipseLink offers superior mapping flexibility with positional and path mappings that allow more complex mapping without introducing additional unnecessary classes to the domain model. | ||
| + | * EclipseLink offers excellent runtime performance. | ||
[[Category:EclipseLink FAQ|MOXy]] | [[Category:EclipseLink FAQ|MOXy]] | ||
Revision as of 20:46, 3 August 2009
What is EclipseLink MOXy?
MOXy is EclipseLink's Object to XML Mapping services. MOXy allows for a POJO object model to be mapped to an XML schema. The Java Architecture for XML Binding (JAXB) provides a Java standard for object XML mapping (OXM). MOXy supports JAXB, as well as providing its' own POJO API and integration with Web Services.
How does EclipseLink MOXy differ from the JAXB reference implementation?
- EclipseLink MOXy provides support externalized mapping metadata. This means that plain old java objects can be mapped onto an XSD without requiring any annotations at all.
- EclipseLink offers superior mapping flexibility with positional and path mappings that allow more complex mapping without introducing additional unnecessary classes to the domain model.
- EclipseLink offers excellent runtime performance.