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/UserGuide/MOXy/Runtime/Bootstrapping Dynamic/Specifying the EclipseLink Runtime"
< EclipseLink | UserGuide | MOXy | Runtime | Bootstrapping Dynamic
(→Instantiating a DynamicJAXBContext) |
(→Instantiating a DynamicJAXBContext) |
||
Line 55: | Line 55: | ||
****<tt>org.w3c.dom.Node</tt> | ****<tt>org.w3c.dom.Node</tt> | ||
****<tt>org.xml.sax.InputSource</tt> | ****<tt>org.xml.sax.InputSource</tt> | ||
− | **** If using | + | **** If using one of these options, a <tt>package-name</tt> element must be defined in the <tt>xml-bindings</tt> element of your OXM file. |
***A <tt>List</tt> of objects from the set above. | ***A <tt>List</tt> of objects from the set above. | ||
**** If using this option, a <tt>package-name</tt> element must be defined in the <tt>xml-bindings</tt> element of your OXM file. | **** If using this option, a <tt>package-name</tt> element must be defined in the <tt>xml-bindings</tt> element of your OXM file. |
Revision as of 18:46, 6 January 2011
EclipseLink MOXy
EclipseLink | |
Website | |
Download | |
Community | |
Mailing List • Forums • IRC • mattermost | |
Issues | |
Open • Help Wanted • Bug Day | |
Contribute | |
Browse Source |
Specifying the EclipseLink Runtime
In order to use EclipseLink Dynamic MOXy as your JAXB implementation, you must identify the EclipseLink DynamicJAXBContextFactory in your jaxb.properties file.
- Create a text file named jaxb.properties, specifying DynamicJAXBContextFactory as the factory used to build new JAXBContexts.
javax.xml.bind.context.factory=org.eclipse.persistence.jaxb.dynamic.DynamicJAXBContextFactory
- Copy the file to your application package (or any of your packages on your classpath).
- Use the standard JAXBContext.newInstance(String contextPath) API to create a DynamicJAXBContext.
DynamicJAXBContext jaxbContext = (DynamicJAXBContext) JAXBContext.newInstance("org.example.mypackage");
Because you do not need to change any application code, you can easily switch between different JAXB implementations.
Instantiating a DynamicJAXBContext
The following methods on JAXBContext can be used to create new instances of DynamicJAXBContexts:
public static JAXBContext newInstance(String contextPath) throws JAXBException public static JAXBContext newInstance(String contextPath, ClassLoader classLoader) throws JAXBException public static JAXBContext newInstance(String contextPath, ClassLoader classLoader, Map<String,?> properties) throws JAXBException
- contextPath - Location of jaxb.properties file.
- classLoader - The application's current class loader, which will be used to first lookup classes to see if they exist before new DynamicTypes are generated.
- properties - A map of properties to use when creating a new DynamicJAXBContext. This map must contain one of the following two keys:
- JAXBContextFactory.XML_SCHEMA_KEY, which can have several possible values:
- One of the following, pointing to your XML Schema file:
- java.io.InputStream
- org.w3c.dom.Node
- javax.xml.transform.Source
- One of the following, pointing to your XML Schema file:
- JAXBContextFactory.ECLIPSELINK_OXM_XML_KEY, which can have several possible values:
- One of the following, pointing to your OXM file:
- java.io.File
- java.io.InputStream
- java.io.Reader
- java.net.URL
- javax.xml.stream.XMLEventReader
- javax.xml.stream.XMLStreamReader
- javax.xml.transform.Source
- org.w3c.dom.Node
- org.xml.sax.InputSource
- If using one of these options, a package-name element must be defined in the xml-bindings element of your OXM file.
- A List of objects from the set above.
- If using this option, a package-name element must be defined in the xml-bindings element of your OXM file.
- A Map<String, Object>, where String is a package name, and Object is the pointer to the OXM file, from the set of possibilities above.
- One of the following, pointing to your OXM file:
- JAXBContextFactory.XML_SCHEMA_KEY, which can have several possible values: