On Mon, Jul 01, 2002 at 01:06:47AM -0400, Sam Ruby wrote: > What is needed, in my mind, is something analogous to > http://www.w3.org/TR/REC-html40/interact/forms.html#h-17.13.1 . Can you > imagine how much less useful HTML FORMS would be if there was no > standard means of representation of control name/control value pairs > provided by the HTML specification? And if each browser and server > application were free to define their own?
I understand what you're getting at, but I think you're missing the point of the new MEP; http://www.w3.org/TR/soap12-part2/#soapresmep The idea is that HTTP GET can be used to retrieve a SOAP envelope. So if we have a URI for a resource; http://some-host.org/my-soap-calendar and I do a GET on it, GET http://some-host.org/my-soap-calendar HTTP/1.1 Host: some-host.org Accept: application/soap+xml then I could get back an XML iCalendar object encapsulated within a SOAP envelope. There is no SOAP request in this case. There is only an HTTP request, and a SOAP/HTTP response. This is how we designed it to be used. Make sense? > Section 4.1.1 of the SOAP 1.2 spec implies that such is out of scope for > the SOAP specifications, and hints to WSDL as the appropriate place. I > can certainly accept this, but lets go full circle and reexamine your > first post to this mailing list: > > > I've had a look through the archives, and haven't found any discussion > > about what the Axis team is thinking about doing to support the > > "Web Method Specification Feature"[1] of SOAP 1.2 when bound to HTTP. > > I'm specifically interested in GET support. > > Perhaps we should be looking to the Web Services Description Working > Group to provide more details first? I don't think that's necessary. SOAP 1.2 is independant of WSDL. MB -- Mark Baker, CTO, Idokorro Mobile (formerly Planetfred) Ottawa, Ontario, CANADA. [EMAIL PROTECTED] http://www.markbaker.ca http://www.idokorro.com
