What I am missing so far is how I define SOAPStruct is in the namespace http://soapinterop.org/xsd. If soapvar was changed to accept something like:
return SoapVar($retobj,'{http://soapinterop.org/xsd}SOAPStruct');
Again.. if you server isn't using soapenc:Struct for any struct encoding then
ALOT of the time it would use a wsdl. And when using wsdl's all the type stuff,
encoding and ns are all behind the scenes.
Based on the premise of always parsing wsdl at run-time I would agree with you. But for any possibility of generating proxies or wrappers based on wsdl, it's an important item.
Just another note, I'm not realy against the server side needing to have wsdl available, but having that on the client side is more an issue since clients may be loaded/unloaded more often.
Shane