Originally noted here: https://bugzilla.redhat.com/show_bug.cgi?id=958884

The issue in 958884 seems to be that the OpenJDK source includes an older version of src/main/java/javax/xml/bind/ContextFinder.java and src/main/java/javax/xml/bind/JAXBContext.java, while the glassfish-jaxb-api has more current versions. The diff is small, but the files are not identical, so the OpenJDK files can't be used by glassfish-jaxb-api. Specifically, there is an added getContextClassLoader() in the newer versions, that changes the behavior for glassfish.

The fixes are specific to glassfish now, but given that the upstream for both items is the same (Oracle Java), I fully expect this is just a temporary out-of-sync issue.

To further that point:

https://jax-ws.java.net/ is the home (note the glassfish ownership)

The OpenJDK readme (http://hg.openjdk.java.net/jdk7/build/raw-file/tip/README-builds.html) says:

The repositories jaxp and jaxws actually do not contain the sources for JAXP or JAX-WS. These products have their own open source procedures at their JAXP and JAX-WS home pages. The OpenJDK project does need access to these sources to build a complete JDK image because JAXP and JAX-WS are part of the JDK. The current process for delivery of the JAXP and JAX-WS sources involves so called "source drop bundles" downloaded from a public website. There are many reasons for this current mechanism, and it is understood that this is not ideal for the open source community. It is possible this process could change in the future.

To make a long ticket short, since this is the core behavior of JAXP/JAX-WS wrt to Glassfish and OpenJDK, and it causes occasional out of sync issues (although, not that affect anything negatively), I propose that we grant an exception for Glassfish (and/or) OpenJDK to bundle JAXP/JAX-WS.