1. Are only some modules allowed within SOAP servers (perhaps for security reasons)?
Yes. See SOAP::Lite to see just what 'dispatch_to' is doing.
2. How can I add additional modules to that list or circumvent the "feature" in #1?
See the SOAP::Lite documentation, especially about what dispatch_to() does. Look for the section labeled SECURITY. I would suggest also looking at soaplite.com, but they're lacking documentation on the subject in question, and just have an empty stub for it... but they do have lots of other info on SOAP::Lite.
3. What sort of code can I ad to my server script or module to tell me what is going on with respect to the module loading or other errors?
It's just a CGI script, so you'll want to look in your webserver's error log for whatever might've been sent to STDERR. You don't want to call print() or the like, or you'll send something back to the client that might be bad. (for debugging those sorts of things, look at on_debug() or passing the +trace or +debug options via use SOAP::Lite +trace; You can also check the assorted fault methods of the SOAP::SOM object that's returned from SOAP::Lite, rather than just checking result():
my $som = SOAP::Lite -> uri('Text/Caps') -> proxy('http://localhost:9000') -> capitalize('Mares Eat Oats, And Does Eat Oats, and Little Lambs + Eat Ivy'); if ( $som->fault() ) { die "ERROR : ",$som->faultcode()," ; ", $som->faultstring(); } my $result = $som->result() || ''
In reply to Re: SOAP Servers and use-ing various modules
by jhourcle
in thread SOAP Servers and use-ing various modules
by geekondemand
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |