Bootstrapping from a Context Path

Another way to bootstrap your JAXBContext is with a String, called the "context path". This is a colon-delimited list of package names containing your mapped classes. Using this approach, there are a few different ways that EclipseLink will discover your model classes:

jaxb.index

The context path could contain a file named jaxb.index, which is a simple text file containing the class names from the current package that will be brought into the JAXBContext:

src/example/jaxb.index:

Employee
PhoneNumber

ObjectFactory

sessions.xml

Bootstrapping from EclipseLink OXM

If you would like to have more control over how your classes will be mapped to XML, you can instead bootstrap from an EclipseLink OXM bindings file. Using this approach, you can take advantage of EclipseLink's robust mappings framework and customize how each complex type in XML maps to its Java counterpart.

Links to the actual OXM files are passed in via the properties parameter, using a special key, JAXBContextFactory.ECLIPSELINK_OXM_XML_KEY. The value of this key will be a handle to the OXM metadata file, in the form of one of the following:

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

When bootstrapping from OXM, the package specified by contextPath must contain a jaxb.properties file that specifies the EclipseLink JAXBContextFactory.