8

Working with a SOAP endpoint. I know it is some .NET server due to the style of stacktrace on exceptions. Nice, a framework where I can expect some type safety granted by static types. I build some xsl to transform the SOAP wsdl files into classes and structs to interact with the endpoint. Works out perfectly.

Plottwist!

Elements which are defined in the xsd/wsdl with maxOccur=unbounded and minOccur=0 should represent a simple collection of this type. Therefore does my implementation expect a collection of this type. But no. The shipped SOAP client in my stack ignores the definition and simply deserializes the SOAP response into T and not a collection of T.

Where the duck are the types when they are defined all over the place?

Comments
  • 0
    Dirty soap, now I've seen everything and I'm ready to die.
  • 2
    @stackler dirty soap is a regular thing.
    - when you live with a car mechanic :)
Add Comment