Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>In the project I'm working on, we're currently redoing our web services completely. These services offer server functionalities to clients via SOAP. From what I've learned looking at all the intricacies of that protocol, which highly affect the layout of the WSDL, I'd rather not write a WSDL myself. There are so many things you can get wrong (especially when it comes to things like parameter style and all that). And once your WSDL "is out there" and clients generated from that WSDL are happily communicating with your application you can no longer change it again (or you start thinking about a versioning strategy, which can turn out to be quite painful as well).</p> <p>So my strong suggestion is to write your service code in Java and let your library generate a WSDL for you. You can then very easily play around with different binding styles (which in turn affect interoperability with other clients). A very thorough article describing all of that can be found here:</p> <p><a href="http://www.ibm.com/developerworks/webservices/library/ws-whichwsdl/" rel="noreferrer">http://www.ibm.com/developerworks/webservices/library/ws-whichwsdl/</a></p> <p>Additionally, WSDLs are not particularly readable for humans and therefore (at least in my view) harder to maintain by humans. Java code on the other hand is fairly easy to read (or at least you can write it that way) which is a even better reason to handcraft the Java code and not the WSDL.</p> <p>Hope that helps in making your decision.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload