Jump to: navigation, search

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

m (fixed links)
Line 6: Line 6:
 
}}
 
}}
 
=Static and Dynamic Entities=
 
=Static and Dynamic Entities=
 
 
  
 
==Using Static MOXy==
 
==Using Static MOXy==
 
 
 
  
 
==Using Dynamic 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.
+
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 as needed, without having to update and recompile the previously-generated Java source code.
  
 
You should consider using Dynamic MOXy when:
 
You should consider using Dynamic MOXy when:
 
*You want EclipseLink to generate classes from an XML schema (XSD).
 
*You want EclipseLink to generate classes from an XML schema (XSD).
 
*You do not want to deal with concrete Java domain classes.
 
*You do not want to deal with concrete Java domain classes.
 
  
 
===Dynamic Entities===
 
===Dynamic Entities===
 
Instead of using actual Java classes (such as <tt>Customer.class</tt> or <tt>Address.class</tt>), Dynamic MOXy uses a simple <tt>get(propertyName)</tt>/<tt>set(propertyName, propertyValue)</tt> API to manipulate data. EclipseLink generates (in memory) a <tt>DynamicType</tt> associated with each <tt>DynamicEntity</tt>.
 
Instead of using actual Java classes (such as <tt>Customer.class</tt> or <tt>Address.class</tt>), Dynamic MOXy uses a simple <tt>get(propertyName)</tt>/<tt>set(propertyName, propertyValue)</tt> API to manipulate data. EclipseLink generates (in memory) a <tt>DynamicType</tt> associated with each <tt>DynamicEntity</tt>.
 
  
 
{{tip||<tt>DynamicTypes</tt> are similar to Java classes; whereas <tt>DynamicEntities</tt> can be thought of as instances of a <tt>DynamicType</tt>.}}
 
{{tip||<tt>DynamicTypes</tt> are similar to Java classes; whereas <tt>DynamicEntities</tt> can be thought of as instances of a <tt>DynamicType</tt>.}}
Line 55: Line 48:
 
**[[EclipseLink/UserGuide/MOXy/Runtime/Bootstrapping/Single_Project/From_sessions.xml_using_DynamicEntities|Single project]]
 
**[[EclipseLink/UserGuide/MOXy/Runtime/Bootstrapping/Single_Project/From_sessions.xml_using_DynamicEntities|Single project]]
 
**[[EclipseLink/MOXy/Runtime/Bootstrapping/Single_Project/From_sessions.xml_using_DynamicEntities|Multiple projects]]
 
**[[EclipseLink/MOXy/Runtime/Bootstrapping/Single_Project/From_sessions.xml_using_DynamicEntities|Multiple projects]]
 
 
  
  

Revision as of 13:29, 11 March 2011

EclipseLink MOXy

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 as needed, without having to update and recompile the previously-generated Java source code.

You should consider using 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 from an XML Schema file (XSD), EclipseLink OXM metadata file, or from an EclipseLink Project specified in the EclipseLink sessions.xml file.


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