Jump to: navigation, search

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

(Overview)
(Overview)
Line 9: Line 9:
 
* '''[[EclipseLink/Examples/MOXy/Dyanmic/DynamicEntityToXml|DynamicEntity to XML]]''' - Learn how to marshal a dyanamic entities to XML.
 
* '''[[EclipseLink/Examples/MOXy/Dyanmic/DynamicEntityToXml|DynamicEntity to XML]]''' - Learn how to marshal a dyanamic entities to XML.
  
[[Category:EclipseLink:Example:MOXy]]
+
[[Category:EclipseLink:Example:MOXy:Dynamic]]

Revision as of 11:02, 21 June 2010

Overview

EclipseLink Dynamic MOXy introduces a new concept in JAXB development - the freedom to bootstrap a JAXBContext from a variety of metadata sources and use familiar JAXB APIs to marshal and unmarshal data, all without having actual compiled domain classes. This enables the metadata to be updated without worrying about updating and recompiling the previously-generated Java source code.

Instead of actual Java classes (e.g. Customer.class, Address.class, etc), the domain objects used in Dynamic MOXy will be subclasses of DynamicEntity. DynamicEntities offer a simple get(propertyName) / set(propertyName, propertyValue) API to manipulate their data. DynamicEntities have an associated DynamicType, which will be generated in memory when the metadata is parsed.