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.
I think probably what we need to do is we need to get developers who are building web services to accept that this isn�t RPC. [�] I have to go to each of the vendors and I have to beat them over the head with a two-by-four to stop making Web services look like RPC calls [but] unfortunately, because these guys make money off of tools, they need to build stuff that is tool oriented.
For example, [when using] Microsoft [�] I annotate it with a special annotation [�] and lo and behold it�s a Web service. EJB 2.1 does the same thing with web services. JSR181 wants to do the same thing. Start from your code, just sprinkle some Web service magic pixie dust on it and lo and behold you have a web service, bad things, bad, bad, bad, bad. I need to beat the vendors over the head to stop doing that, to instead make tools, build tools that want to look at and see and recognize that:
this is a message, and
it�s in XML, because wanting to take your code and seamlessly turning it into objects and back again, [�] that�s just not going to work. It�s not going to happen.
Music to my ears.
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