Skip to main content
Jump to: navigation, search

EclipseLink/UserGuide/MOXy/Runtime/Specifying the EclipseLink Runtime

< EclipseLink‎ | UserGuide‎ | MOXy‎ | Runtime
Revision as of 12:55, 6 January 2011 by (Talk | contribs) (Instantiating a DynamicJAXBContext)

EclipseLink MOXy

Mailing ListForumsIRCmattermost
OpenHelp WantedBug Day
Browse Source

Specifying the EclipseLink Runtime

In order to use EclipseLink MOXy as your JAXB implementation, you must identify the EclipseLink JAXBContextFactory in your file.

  1. Create a text file named, specifying JAXBContextFactory as the factory used to build new JAXBContexts.
  2. Copy the file to the same package (directory) in which your model classes reside.
  3. Use the standard JAXBContext.newInstance(Class... classesToBeBound) API to create a JAXBContext.
    JAXBContext jaxbContext = JAXBContext.newInstance(Customer.class);

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 JAXBContextFactory can be used to create JAXBContexts:

public static JAXBContext newInstance(Class... classesToBeBound) throws JAXBException
public static JAXBContext newInstance(Class[] classesToBeBound, Map<String,?> properties) throws JAXBException
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
  • classesToBeBound - List of Java classes to be recognized by the new JAXBContext.
  • contextPath - List of Java package names that contain mapped classes.
  • classLoader - The class loader used to locate the mapped classes.
  • properties - A map of additional properties.

Version: 2.2.0 DRAFT
Other versions...

Back to the top