Question

The jaxb.properties needs to be in the same package as the domain classes you are creating the JAXBContext on.

I am using Moxy’s xml driven configuration since I doesn’t want to use annotations or XJC generated objects. I have an existing domain classes that are spread across multiple packages. Does this mean that i need to have the jaxb.properties present in all those packages or there is a better alternative (Maybe writing my own implementation of some interface that can read from a jvm arg or something)?

Answer 1

Does this mean that i need to have the jaxb.properties present in all
those packages?

If you are creating your JAXBContext on classes, then you need to have a jaxb.properties file in at least one of the packages of the domain classes passed in. In the example below you could have a jaxb.properties file in either package1 or package2.

JAXBContext jc = JAXBContext.newInstance(package1.Foo.class, package2.Bar.class);

If you are creating your JAXBContext on package names, then you need to have a jaxb.properties files in at least one of the packages. Note that packages are separated by a ‘:’.

JAXBContext jc = JAXBContext.newInstance("package1:package2");

---

or there is a better alternative

My preference is to use the standard JAXB APIs with a jaxb.properties file to specify MOXy as the JAXB provider. Some people prefer using the native MOXy APIs to do this:

JAXBContext jc = org.eclipse.persistence.jaxb.JAXBContextFactory.createContext(new Class[] {Foo.class, Bar.class}, null);

---

For More Information

• http://blog.bdoughan.com/2011/05/specifying-eclipselink-moxy-as-your.html