Bug 1468172

Summary: [GSS](6.4.z]) SOAP - JAXB validation - fault when adding additional elements
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Francesco Marchioni <fmarchio>
Component: Web ServicesAssignee: Peter Palaga <ppalaga>
Status: CLOSED WONTFIX QA Contact: Peter Mackay <pmackay>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4.9CC: asoldano, bmaxwell, fmarchio, ppalaga
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-07-13 18:00:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Test Web service
none
SOAP input message to test the Web service none

Description Francesco Marchioni 2017-07-06 07:26:16 UTC 
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):
6.4.z

How reproducible:

Example request:
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:wor="http://ws.bitmarck-software.de/framework/workflow/WorkflowBusinessWS">
   <soap:Header/>
   <soap:Body>
      <wor:setActivityStatus>
         <ActivityInstanceOid>3</ActivityInstanceOid>
         
         <MyTest>Hugo</MyTest>
         
      </wor:setActivityStatus>
   </soap:Body>
</soap:Envelope>

The element MyTest is additional and not part of WSDL.


Additional info:
Related case: 01743954
Comment 2 Francesco Marchioni 2017-07-12 11:15:27 UTC 
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.
Comment 3 Francesco Marchioni 2017-07-12 11:16:04 UTC 
Created attachment 1296877 [details]
Test Web service
Comment 4 Francesco Marchioni 2017-07-12 11:21:52 UTC 
Created attachment 1296879 [details]
SOAP input message to test the Web service
Comment 5 Peter Palaga 2017-07-13 13:30:20 UTC 
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.
Comment 6 Brad Maxwell 2017-07-13 18:00:58 UTC 
Closing as per previous comment