Difference between revisions of "EclipseLink/UserGuide/MOXy/Overview/DynamicEntities"

From Eclipsepedia

Jump to: navigation, search
m
m
Line 4: Line 4:
 
=Static and Dynamic Entities=
 
=Static and Dynamic Entities=
  
* [[#static|Static Entities]
+
* [[#static|Static Entities]]
* [[#dynamic|Dynamic Entities]
+
* [[#dynamic|Dynamic Entities]]
  
  
Line 39: Line 39:
 
customer.set("address", address);
 
customer.set("address", address);
 
</source>
 
</source>
 +
{{Template:EclipseLink_Spec
 +
|section=Appendix D: Binding XML Names to Java Identifiers
 +
}}
  
  
Line 51: Line 54:
 
**[[UserGuide/MOXy/Runtime/Bootstrapping/Single_Project/From_sessions.xml_using_DynamicEntities|Multiple projects]]
 
**[[UserGuide/MOXy/Runtime/Bootstrapping/Single_Project/From_sessions.xml_using_DynamicEntities|Multiple projects]]
  
{{Template:EclipseLink_Spec
 
|section=Appendix D: Binding XML Names to Java Identifiers
 
}}
 
  
  

Revision as of 10:31, 10 December 2010


link="http://wiki.eclipse.org/EclipseLink"
EclipseLink
Website
Download
Community
Mailing ListForumsIRC
Bugzilla
Open
Help Wanted
Bug Day
Contribute
Browse Source

Static and Dynamic Entities


Using Static MOXy

Using Dynamic MOXy

With EclipseLink Dynamic MOXy, you can bootstrap a JAXBContext from a variety of metadata sources and use existing JAXB APIs to marshal and unmarshal data… without having compiled Java class files on the classpath. This allows you to alter the metadata source as needed, without having to update and recompile the previously-generated Java source code.

You should consider using [#Dynamic Entities|Dynamic MOXy] when:

  • You want EclipseLink to generate classes from an XML schema (XSD).
  • You do not want to deal with concrete Java domain classes.


Dynamic Entities

Instead of using actual Java classes (such as Customer.class or Address.class), dynamic MOXy uses a simple get(propertyName)/set(propertyName, propertyValue) API to manipulate data. EclipseLInk generates (in memory) a DynamicType associated with each DynamicEntity

Idea.png
DynamicTypes are similar to Java classes; whereas DynamicEntities can be thought of as instances of a DynamicType.


Example

DynamicEntity customer = (DynamicEntity) dynamicJAXBContext.createUnmarshaller().unmarshal(instanceDoc);
 
String lastName = customer.get("lastName");
List orders = customer.get("orders");
...
DynamicEntity address = dContext.newDynamicEntity("mynamespace.Address");
address.set("street", "1001 Fleet St.");
 
customer.set("lastName", lastName + "Jr.");
customer.set("address", address);
Elug javaspec icon.gif

For more information, see Appendix D: Binding XML Names to Java Identifiers in the JPA Specification.


Creating Dynamic Entities

To create and use Dynamic MOXy entities, create a JAXBContext by using the DynamicJAXBContextFactory class. You can create a DynamicJAXBContext can be created from an XML Schema file (XSD), EclipseLink OXM metadata file, or from an EclipseLink Project specified in the EclipseLink sessions.xml file.
Note: DynamicJAXBContexts cannot be instantiated directly, they must be created through the factory API.



Eclipselink-logo.gif
Version: 2.2.0 Draft
Other versions...