|Just another Perl shrine|
Problem with PerlTransHandlerby rob_au (Abbot)
|on Jun 07, 2004 at 05:31 UTC||Need Help??|
rob_au has asked for the
wisdom of the Perl Monks concerning the following question:
I have a fairly convoluted problem which appears to result from an interaction with a PerlTransHandler and SOAP::Lite.
The scenario is that I have a set of web servers, running Apache 1.3.29/mod_perl 1.29, serving a number of virtual host configurations for various service interfaces. One of these virtual host configurations (virtual host A) employs SOAP::Lite (specifically Apache::SOAP) to provide a SOAP interface to some web services which are currently under development. By itself, this configuration is behaving correctly and without issue.
Upon establishing a configuration for a new virtual host (virtual host B) which employs a PerlTransHandler for service redirection however, errors are returned when attempting to access the SOAP::Lite services on the existing virtual host (virtual host A). The errors returned from the SOAP::Lite interface are of the form "Failed to locate method (MySoapMethod) in class (MySoapClass) at /opt/lib/perl5/site_perl/5.6.2/SOAP/Lite.pm line 2337". Removing the PerlTransHandler configuration from the new virtual host configuration (for virtual host B) rectifies this problem.
My question is how should I solve this conflict? Both of these virtual host services are required and cannot be omitted from the server configuration.
One thought which I had was to attempt to limit the scope of execution of the PerlTransHandler, but after doing a bit of research, I have found that the <Location> and <Directory> directives cannot be used to reduce the scope of PerlTransHandler execution (although I have not found any documentation as yet which correlates with my observation of PerlTransHandler execution across virtual hosts). Indeed, the recommended manner by by which to limit the application of PerlTransHandler is through the employ of location-specific attributes - For example:
perl -le "print unpack'N', pack'B32', '00000000000000000000001011100000'"