Re: [SOAP] Seperating SOAP_WSDL

I'd be all for seperating them, in fact that should be done, but both classes need to be rewritten for that to happen, as they currently are dependent on specifics of PEAR::SOAP. Shane Harry Fuecks wrote:

More a question for Shane but wondering if there's any possibility of seperating SOAP_WSDL (and SOAP_Disco) from the rest of the library? There's a few reasons why it might be a good idea (although I realise it's probably alot of work).

From a general point of view, the WSDL spec. suggests that WSDL is meant to

be independent of underlying protocols. So far that's not really being used although .NET does generate WSDL for services using the HTTP bindings for GET requests. One example is here: http://www.webservicex.net/usweather.asmx?WSDL Also, given how mature SOAP_WSDL is, might be able to give a helping hand to other SOAP implementations, such as generating client proxy code. Had a play with doing this for eZSOAP here: http://www.phppatterns.com/index.php/article/articleview/40/1/2/ Anyway - just an idea. Please feel free to ignore.