all bits considered data to information to knowledge


Who’s got Web Services right

Once in a while, Microsoft does the right thing, and the rest of the programming community ought to simply acknowledge the contribution, and move forward. Consider web services: creating a webservice in .Net is [almost] as easy as marking a function with WebMethod attribute .

Here're some well taken points emanating from Mark D. Hansen - a bona fide Java developer and architect (and the author of SOA Using Java Web Services book)

"Adding web services to Java applications should not require programming. There should be a simple ON/OFF switch. You should be able to select some business logic, flip the ON switch, and publish it as a web service.  Unfortunately, Java isn’t designed that way. Java requires you to write code, annotate classes, recompile, and redeploy. And it isn’t simple coding either[md]particularly when you run into problems with Java/XML serialization."

Mark goes on quoting in his book the blog of Dave Podnar - a hilarious summation of the problem!

Dave Podnar's Five Stages of Dealing with Web Services

1. Denial: It's Simple Object Access Protocol, right?
2. Over-Involvement: OK, I'll read the SOAP, WSDL, WS-I BP, JAX-WS, SAAJ, JAXB, … specs. Next, I'll check the wiki and finally follow an example showing service and client sides.
3. Anger: I can't believe those
#$%&*@s made it so difficult!

I could not find the remaining two stages on the Net, but would speculate that they either deal with either reaching nirvana or switching to COBOL programming...