JAXB is used to :
- generate classes from xsd schemas
- parse xml files to Java objects
The generator uses the maven-jaxb2-plugin that uses the latest version of jaxb (2.2.11 right now).
The parser, which relies on JAXBContext and SPI (the META-INF/services thing) resolution, uses whatever is available in the classpath.
Sometimes it is JAXB bundled with Java 7 (2.2.4-1 right now) and sometimes it is JAXB-RI present as a dependency (com.sun.xml.bind:jaxb-impl, version 2.2.4-1 as set in the parent pom).
It would make sense to always use JAXB-RI version 2.2.11 as it is the latest.
Changes would imply:
- using the new groupId org.glassfish.jaxb and new artifactIds jaxb-core, jaxb-runtime and jaxb-xjc.
- excluding jaxb-api (first check if it is incompatible about the one in Java 7).
- verify all the dependencies that relies on jaxb (for example by blacklisting in the enforcer the old groupId and replace the dependencies), including easycommons and easywsdl
Advantages would be to have more coherence everywhere and potential bug fixed.