The version of sun jaxb that we are currently using is a couple of years old. QE requested an upgrade to a more recent version in bug #1070281. The current stable version is 2.2.7 which is two micro versions newer than our current version (2.2.5). Release notes for version 2.2.6 https://java.net/jira/secure/ReleaseNote.jspa?projectId=10198&version=15724 for 2.2.7 https://java.net/jira/secure/ReleaseNote.jspa?projectId=10198&version=15930
BZ 1070281 has all acks ++ blocker + ... this should be fixed as soon as possible
BZ 1070281 requested to sync it with upstream which is using 2.2.6 Adding Alessio for feedback about move to 2.2.7 JBossWS CXF trunk is on 2.2.6 - http://anonsvn.jboss.org/repos/jbossws/stack/cxf/trunk/pom.xml <jaxb.impl.version>2.2.6</jaxb.impl.version>
JBossWS trunk is now on 2.2.7 - https://issues.jboss.org/browse/JBWS-3799 <asoldano> rsvoboda, there should not be problems; anyway I'm moving our trunk to 2.2.7 right now So upgrade to 2.2.7 in EAP is fine.
FYI - blocker? added because BZ 1070281 has blocker +
To provide some additional information regarding the risk of this upgrade, there was an upstream issue to refactor the jars in 2.2.7. https://java.net/jira/browse/JAXB-912 We should be able to get this upgrade into the upstream wildfly sources (WFLY-3372), and test it there before consuming the upgrade in EAP.
EAP 7.0 has jaxb 2.2.11