AW: [Xml-compile] Resilience to random WSDL changes

[Michael Ludwig]

> Von: Mark Blackman
> On 1 Mar 2012, at 16:44, Mark Blackman wrote:
> > 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:

> More specifically, this is because the WSDL used to intrepret the
> response is probably declaring a complex type composed of an
> XML-Schema "sequence" type where order matters. You could use your
> own copy of the WSDL but change it to "all" instead of "sequence".

Patching the WSDL myself might be a good approach. Thanks!

The changes are like this:

+ <s:element minOccurs="0" maxOccurs="1" name="SellerCountry" type="s:string" />

- <s:element minOccurs="1" maxOccurs="1" name="CreationDate" type="s:dateTime" />

- <s:element minOccurs="1" maxOccurs="1" name="Age" type="s:int" />
- <s:element minOccurs="1" maxOccurs="1" name="Gender" type="s:unsignedByte" />

- <s:attribute name="FileLength" type="s:int" />

So if I make elements I don't need optional the library won't complain
about them missing.

Michael