Red Hat Bugzilla – Bug 1468172
[GSS](6.4.z]) SOAP - JAXB validation - fault when adding additional elements
Last modified: 2017-07-14 09:24:37 EDT
Description of problem:
When sending a SOAP request with additional elements, it results in a Fault reporting an Unmarshalling Error because of unexpected element. This causes compatibility issues for applications migrated from EAP 5, where additional SOAP elements are ignored.
Version-Release number of selected component (if applicable):
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:wor="http://ws.bitmarck-software.de/framework/workflow/WorkflowBusinessWS">
The element MyTest is additional and not part of WSDL.
Related case: 01743954
Ok, I'm attaching the Webservice used to test which is anyway a minimal HelloWorld web service.
I'm also attaching the SOAP request and response.
Created attachment 1296877 [details]
Test Web service
Created attachment 1296879 [details]
SOAP input message to test the Web service
I prepared a workaround based on ValidationEventHandler that ignores just the unexpected elements: https://github.com/ppalaga/JBEAP-11984-jaxb-addional-elems
The workaround is all we can offer. Setting dev_nack because we are not obligated to keep 100% backwards compatibility between major versions. Moreover, it is quite late to ask for this late phase of EAP 6 life cycle.
Closing as per previous comment