Mark, Thanks for the clarification; sorry to everybody for the noise. I'd seen a demo of the .NET GET-based request but didn't realize it wasn't returning a SOAP envelope. Here is a sample service I found that accepts GET and POST requests of the type you describe, as well as SOAP requests. It shows sample requests and responses that prove I didn't know what I was talking about. Anyway, I'll try to think more, write less--
It occurs to me that Sudhir's original question was answered here: http://marc.theaimsgroup.com/?l=axis-user&m=101948904722368&w=2 Andrew At 02:34 PM 5/21/2002 -0500, you wrote: >Hi Andrew and Sudhir: > >Reading through this thread, I think there's a bit of confusion (it could be >mine of course). > >I don't believe that it is true that all web service requests and responses >must be sent in SOAP. When the WSDL 1.1 spec talks about HTTP GET/POST >bindings, I don't think it is talking about SOAP at all. I've read at least >one article lately that talks about how SOAP is a big waste of bandwidth, >and that argues that web service requests should be sent as URLs (with >arguments inline) and responses as SOAP-free XML documents in an HTTP >response. I think it was over on the O'Reilly XML website (www.xml.com). > >If you use MS.Net to produce a simple web service that just returns a hello >world string, you'll see that the HTTP GET/POST response message is not a >SOAP message at all -- it is simply an xml document with an element >containing the string (there is no SOAP envelope). > >So using HTTP GET, with your web service request data in the URL header, or >POST with them in the message body, and getting back the response as a >SOAP-free HTTP message is probably not just MS showing off, and I doubt the >intention was just for easy testing. > >I believe it is orthogonal to SOAP. > > >Cheers, > >Mark Young >Omniopera: XML Schema and WSDL Authoring Software >http://www.omniopera.com
