You're right. I think the problem may be with the client.
From soaplite cookbook:
Dynamic
As you can see in both Static internal and Static external modes the name of the module is hardcoded in the server's code. But what if you want to be able to add new modules dynamically without changing the code? Dynamic dispatch allows you to do that. Specify the directory and any module in this directory becomes available for dispatching: 3.c. server (Dynamic) (hibyedyn.cgi)
#!perl -w
use SOAP::Transport::HTTP;
SOAP::Transport::HTTP::CGI
-> dispatch_to('/home/soaplite/modules')
-> handle;
Then put Demo.pm in /home/soaplite/modules directory:
That's it. The any module you put in /home/soaplite/modules is now available, but don't forget that the URI on the client side should match the module/class name you want to dispatch your call to.
Hope this helps.
-Lee
"To be civilized is to deny one's nature."