Creating a webservice has become a chore. In fact, it has never been exciting. There are just too many things to do and too many things that can go wrong. Starting with the WSDL, defining the service poses just too many posibility of making errors. Namespaces can go wrong; the WSDL can be WS-* non-compliant; even with WS-* compliance, Java can possibly generate difficult to use endpoints, or .NET not generating the expected proxy classes. This is certainly not recommended for the non-technically inclined. You create either a mess or an art, a painful piece of art.
Having adopted the development process of WSDL-to-Java, I start to wonder if the opposite way might have been easier. Just define the endpoints in my Java codes, and let the tool generate the (supposedly) WS-* compliant WSDL. Certainly I won't have as much control over the WSDL and XSD generated, but doing it this way will help to negate the need for designers to know the technical details of WSDL and XSD. Note that not all designers are technically inclined or trained, which I've always wonder why are they not so.
No comments:
Post a Comment