Web services best practices is moving away from RPC and towards doc/literal
Originally posted by Thomas Hatley:
As a developer who is just finishing a project which exposes a Java-based service to .Net consumers/clients, I found that the many quick-n-easy tutorials of RPC services returning simple types seemed to do Java developers more of an injustice rather than helping................
.................beginning developers up for failure shortly down the road whent their help desk phone rings saying "a new .Net company can't digest our service...now what?" and the beaming-proudly-just-a-minute-ago developer is totally lost.
Originally posted by William Brogden:
So what do you see as the main sticking points that are forcing this move? Are people giving up on the basic SOAP premise or what?
establish hype-free SOA value propositions which can be accomplished by identifying and describing how SOA addresses client-specific pain points or business challenges.
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.