Re: SOAP and WSDL

Sure it makes sence. Same with UDDI if it ever gets implemented. Right now, the WSDL class probably has some dependencies that need to be removed, and there is still some significant schema work that needs to be done. The webservice class has been tossed around also. Yannick Loiseau wrote:

Hello all, I've got some remarks about SOAP and WSDL... Excuse me if the question have already be discussed. It seems that the WSDL class is include in the SOAP package. Theorically, WSDL is independent of the protocol the service uses, it only describe the service, and indicate the protocol. Obviously, SOAP is the most used, but it can be XML-RPC, pure HTTP (see REST) and so on. WSDL provide only a description of the binding. In a proper implementation of WSDL, the user don't even have to care about the service protocol, as the binding is done later. See for example WSDL "client" in C#, Java or Perl. The user just have to provide the WSDL uri and call methods... that's it. My suggestion is to make the WSDL class independent, to allow future implementation of REST, XML-RPC,etc. and possibly to generalize SOAP and XML-RPC in a "WebService" virtual Class, calling a common WSDL. Does it make sense ?