Can I avoid 'Unexpected subelement' errors when the service-provider introduces new properties?
I have a soap client call that invokes a remote service. Unfortunately the service provider is updating the service definition frequently and introduces new properties or changes the property order. Therefore I can no longer call it, the mapping of the response fails with:
ADBException: Unexpected subelement theID
Exception: org.apache.axis2.databinding.ADBException: Unexpected subelement theID
AxisFault: org.apache.axis2.databinding.ADBException: Unexpected subelement theID
BpmError: ivy:error:webservice:exception
RequestException: ivy:error:webservice:exception
Problem while processing request 'http://127.0.0.1:8081/ivy/pro/designer/finElcaUser/163B11CD193F9801/start.ivp'
I've also tried the new Webservice stack of Axon.ivy 7.1 based on CXF. But it fails with a similar issue:
UnmarshalException: unexpected element (uri:"", local:"theID"). Expected elements are <{}firstname>,<{}lastname>
SAXParseException2: unexpected element (uri:"", local:"theID"). Expected elements are <{}firstname>,<{}lastname>
javax.xml.bind.UnmarshalException
- with linked exception:
[com.sun.istack.internal.SAXParseException2; lineNumber: 1; columnNumber: 218; unexpected element (uri:"", local:"theID"). Expected elements are <{}firstname>,<{}lastname>]
Fault: Unmarshalling Error: unexpected element (uri:"", local:"theID"). Expected elements are <{}firstname>,<{}lastname>
Web Service Element: Call to http://localhost:8082/ivy/ws/designer/elcaMock/163B11ABE3388EE4 (Operation[name=getPersons,port=DocServicePort,parameters=[]]) failed!
**Is there any way to read the response in a compliant way and ignore new properties introduced by the provider?**provider?**
the roundtrip is huge if I have to re-generate the client stack every-time when the provider makes changes.