comment on

Not really sure, but my guess would be that it has to do with the following piece of code (SOAP/Lite.pm, line 2500):

  unless (defined(%{"${class}::"}) || exists($INC{join '/', split /::/
+, $class.'.pm'})) {
    # allow all for static and only specified path for dynamic binding
+s
    local @INC = (($static ? @INC : ()), grep {!ref && m![/\\.]!} $sel
+f->dispatch_to);
    eval 'local $^W; ' . "require $class";

    die "Failed to access class ($class): $@" if $@;
    $self->dispatched($class) unless $static;
  }
[download]

in particular the local @INC = ...

A cursory glance at the surrounding lines makes me wonder what would happen if you "preload" Data::Dumper in the server (the idea being that it then already is loaded when the require is executed with the restricted @INC...). Just an idea - could be entirely wrong, though.

In reply to Re: @INC problem with SOAP::Lite by almut
in thread @INC problem with SOAP::Lite by john_oshea

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Don't ask to ask, just ask
	PerlMonks