This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Stepping onto the new web services island one might think "Oh brave new world that has such wonders." Then the reality of web services sets-in. Dozens of platform providers, independent software vendors, and utility software developers have implemented web services protocols (SOAP, WSDL, and UDDI) in their products. While the protocols are now nearly two years old and working drafts of the next specifications (SOAP 1.2 for example) are in the works, developers have had to interpreted the meaning in parts of the specifications. Interpretation allows interoperability problems to seep into SOAP-based web services.
Web service interoperability goals are to provide seamless and automatic connections from one software application to another. SOAP, WSDL, and UDDI protocols define a self-describing way to discover and call a method in a software application -- regardless of location or platform. Data is marshaled into XML request and response documents and moved between software packages using HTTP or message-based protocols. Interoperability problems creep in at the discovery, definition, and request/response mechanisms.
William Butler Yeats: All life is a preparation for something that probably will never happen. Unless you make it happen.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com