Why do you need autodispatch? There appears to be a tradeoff here. On one hand is autodispatch for when you have the proxy info at compile time. On the other is the regular dispatch where you can specify all that exactly where you need it, but can do so dynamically.
It appears that you want your cake and you want to eat it, too. From a cursory glance at the SOAP::Lite docs, it does not appear that SOAP::Lite allows for that.
That said, you might be able to do your own imports...
That might work - hopefully there aren't any functions with prototypes in there ... although I have to admit that I doubt that to be the case. There may be other gotchas, too, I'm not sure.use SOAP::Lite; SOAP::Lite->import(autodispatch => uri => $uri, proxy => $proxy, # etc... );
In reply to Re^3: Problems creating a SOAP::Lite client
by Tanktalus
in thread Problems creating a SOAP::Lite client
by robert.heise
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |