Ah, it all becomes a lot clearer now. After reading the MSDN article I also understand yesterday's post about SOAP not needing WSDL and vise versa. The fact that AXIS being a SOAP toolkit only supports the SOAP binding for WSDL is only logical. (That doesn't mean I wouldn't still like GET and POST bindings but I can live with the fact that the tasks may be at the bottom of the pile :-)
> -----Original Message----- > From: Steve Loughran [mailto:[EMAIL PROTECTED]] > Sent: woensdag 22 mei 2002 1:59 > To: [EMAIL PROTECTED] > Subject: Re: Clients using GET and POST > > > > ----- Original Message ----- > From: "Tako Schotanus" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, May 21, 2002 4:06 PM > Subject: RE: Clients using GET and POST > > > Why did it work in beta 1 and not in beta 2? > > no idea. > > > Did the people working on AXIS development think the same > thing as you? > > > > "Hey, a text-based GET/POST request is not SOAP so let's > take it out." ? > > > > no idea. > > but I do know that it isnt SOAP, so probably got to the bottom of the > priority list. I also know that other people are also saying > for interop, > avoid GET and POST, and even tell you how to stop .NET from > generating those > stubs: > > http://msdn.microsoft.com/library/en-us/dn_voices_webservice/h tml/service120 52001.asp?frame=true
