SOAP Blueprint, or How I Learned to Stop Worrying and Love WSDLs
Published:
If you have ever had to write a WSDL file by hand, you know that the experience sits somewhere between filling in a tax form and defusing a bomb. One misplaced namespace, one wrong nesting style, and the consuming system rejects the whole thing with an error message that tells you absolutely nothing useful. If that consuming system happens to be SAP, the error messages may get even more cryptic and they come individually, even though there are ways of knowing where the problems lay. Furthermore, the documentation on what WSDL structure SAP actually expects is a mixture of tribal knowledge and a bunch of SAP Notes.