Altova Mailing List Archives

Re: [xml-dev] Can you stand yet another SOAP-RPC vs HTTP GET question?

From: "Thomas B. Passin" <tpassin@-------.--->
To: xml-dev@-----.---.---
Date: 4/20/2002 4:02:00 PM
[Mike Champion]

> Ah-ha, I think that's what I've been missing here!  Never having used VB,
> I just didn't grok why people would want to jump through hoops to avoid
> with a very simple URI/HTTP call/XML result.  That just doesn't fit into
> "paradigm" of visual component assembly programming, but WSDL/SOAP-RPC
> And the "hoops" are hidden out of sight, along with all the other code
> that VB is doing.

I've just starting working with .NET Studio and their Services.  It's quite
amazing what goes on behind the scenes.  You can, BTW, create a wsdl page
for a perfectly normal RESTFUL GET or POST page.  The .NET Studio machinery
can take that wsdl and use it to create client web pages in the exact same
way as follow for SOAP services.  To the programmer, nothing much has
changed, but behind the scenes the Microsoft .NET machinery uses a GET or a
POST.  So far as I know so far, the POST has to return an xml document
(could be a single element, of course) that is defined in a schema in the
wsdl document.

Within Studio, you instantiate an object representing the service, and call
methods on it as if it were an ordinary object.  It seems innocent enough,
but you are totally divorced from what really goes on behind the scenes -
including several layers of hidden code the system generates.


Tom P


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.