Bug 1468172 - [GSS](6.4.z]) SOAP - JAXB validation - fault when adding additional elements
Summary: [GSS](6.4.z]) SOAP - JAXB validation - fault when adding additional elements
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Services
Version: 6.4.9
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Peter Palaga
QA Contact: Peter Mackay
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-06 07:26 UTC by Francesco Marchioni
Modified: 2020-08-13 09:35 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-07-13 18:00:58 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Test Web service (185 bytes, text/plain)
2017-07-12 11:16 UTC, Francesco Marchioni
no flags Details
SOAP input message to test the Web service (895 bytes, text/plain)
2017-07-12 11:21 UTC, Francesco Marchioni
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEAP-11984 0 Major Closed [GSS] (EAP 7.1.z) SOAP - JAXB validation - fault when adding additional elements 2019-07-16 17:00:40 UTC
Red Hat Knowledge Base (Solution) 3114701 0 None None None 2017-07-14 13:24:36 UTC

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


Note You need to log in before you can comment on or make changes to this bug.