How should I compensate for a bad WSDL?

Posted by Brabster on Stack Overflow See other posts from Stack Overflow or by Brabster
Published on 2009-09-24T14:07:13Z Indexed on 2010/03/21 16:51 UTC
Read the original article Hit count: 332

Filed under:
|
|
|
|

I've come across several examples of SOAP-based web services where automated tooling fails to build a client that works.

Investigating these examples leads me to believe that the WSDL the service uses to describe itself doesn't quite match the service that's being provided. Maybe a wrong type somewhere, a different data structure - something.

I'm unsure what the most appropriate response is - if we assume that the obvious one (get the provider to fix their stuff) isn't available.

Some options I can think of:

  • Make a fixed WSDL?
  • Hack the generated code?
  • Any other options?
  • No good options?

What good experiences have people had? What works in a real environment?

Thanks

© Stack Overflow or respective owner

Related posts about web-services

Related posts about wsdl