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

Michael Ludwig m.ludwig at epages.com
Fri Mar 2 13:03:22 GMT 2012


> Von: Mark Overmeer
> Gesendet: Donnerstag, 1. März 2012 20:18

> Poor design.

Yes. I agree with all your observations below. And that's only
the tip of the iceberg.

I guess it's just the usual case with webshops. Inexperienced
developers, tight schedules, no time for refactoring. People
just doing their job. You get what you pay for. Well, in the
case of published APIs, the hapless integrator also pays.

Best,

Michael

> * Michael Ludwig (m.ludwig at epages.com) [120301 17:05]:
> > + <s:element minOccurs="0" maxOccurs="1" name="SellerCountry"
> type="s:string" />
> 
>    <seller>
>       <country>
> 
> > - <s:element minOccurs="1" maxOccurs="1" name="Age" type="s:int" />
> 
>   unsignedByte seems sufficient ;-)  Not minimal 10 digit signed ;-)
> 
> > - <s:element minOccurs="1" maxOccurs="1" name="Gender"
> type="s:unsignedByte" />
> 
>   Gender 1 ?  What's wrong with enumerations?
> 
> > - <s:attribute name="FileLength" type="s:int" />
> 
>   unsignedLong?



More information about the Xml-compile mailing list