Based on asoldano comment: https://bugzilla.redhat.com/show_bug.cgi?id=1151526#c17
'My opinion is that we need a CXF jira for the changes not strictly related to our JBossWS SOAPConnectionImpl (it should be checked if the Soap11FaultInInterceptor should actually be rejecting http 400 messages) and a JBWS jira for the rest of the changes.'
Re-Add to WS upgrade and 6.4.2 payload
https://issues.apache.org/jira/browse/CXF-6198 still unresolved, upstream is not sure how to proceed.
Removing from eap642-payload and JBossWS CXF 4.3.5.Final component upgrade BZ. Discussed via email with Bartosz a Alessio, no upstream activity. Changes won't be merged, we will wait for action from CXF team.
JBossWS CXF 4.3.5.Final tag is already available - http://anonsvn.jboss.org/repos/jbossws/stack/cxf/tags/jbossws-cxf-4.3.5.Final
*** This bug has been marked as a duplicate of bug 1182919 ***