Autodispatch uses UNIVERSAL::AUTOLOAD which catches all unknown method calls. It enables you to call remote functions with the same syntax as local ones. All calls to undefined methods will result in an attempt to use SOAP.
This is form the documentation: WARNING: autodispatch feature can have side effects for your application and can affect functionality of other modules/libraries because of overloading UNIVERSAL::AUTOLOAD. All unresolved calls will be dispatched as SOAP calls, however it could be not what you want in some cases. If so, consider using object interface (see implementation of OO interface). -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of darren chamberlain Sent: 22 January 2003 03:01 To: [EMAIL PROTECTED] Subject: Re: [Templates] soaplite * Mark Proctor <m.proctor at bigfoot.com> [2003-01-21 20:26]: > I have changed it from autodispatch to explicit object calling, it > seems to work fine now. So there is definitely a problem with template > toolkit working with soaplite autodispatch feature. Save me from `perldoc SOAP::Lite` -- what is the autodispatch feature, and how might it interact with TT? (darren) -- The limits of my language mean the limits of my world. -- Ludwig Wittgenstein _______________________________________________ templates mailing list [EMAIL PROTECTED] http://lists.ourshack.com/mailman/listinfo/templates _______________________________________________ templates mailing list [EMAIL PROTECTED] http://lists.ourshack.com/mailman/listinfo/templates
