[Xml-compile] Resilience to random WSDL changes

Mark Blackman m.blackman at fairfx.com
Thu Mar 1 16:44:18 GMT 2012


On 1 Mar 2012, at 16:35, Michael Ludwig wrote:

> The provider of the service I'm interfacing with sometimes makes
> random changes to the published WSDL and the implementation behind.
> Unsurprisingly, processing then fails:
> 
> error: decode error: data for element or block starting with `Age' missing at {http://superlister.aucland.com/QxlRicardoServices/}CheckAccountResponse/CheckAccountResult
> Errors while decoding:
>  error: decode error: data for element or block starting with `Age' missing at {http://superlister.aucland.com/QxlRicardoServices/}CheckAccountResponse/CheckAccountResult
> error: decode error: data for element or block starting with `Age' missing at {http://superlister.aucland.com/QxlRicardoServices/}CheckAccountResponse/CheckAccountResult
> Errors while decoding:
>  error: decode error: data for element or block starting with `Age' missing at {http://superlister.aucland.com/QxlRicardoServices/}CheckAccountResponse/CheckAccountResult

We usually see this when they add a new element at the same level and the relative index
for the 'Age' element has changed but is still present.  I presume the SOAP spec. is
fussy about order of elements, but I have only recently appreciated that.

- Mark


More information about the Xml-compile mailing list