On Mon, Aug 21, 2000 at 05:44:15PM +0200, Andre Landwehr wrote:
> "PerlSetEnv EMBPERL_OBJECT_ADDPATH :/home/httpd/145.228.6.167/components:"
> in my httpd.conf, but this is what is logged in embperl.log:
> (...)
Forget my previous postings, I had a really dumb mistake in the
ADDPATH I specified in my httpd.conf (missed a directory..)
Sorry for the inconvenience!
But nevertheless there seems to be sth. wrong with the addpath
feature:
as I said earlier I want to Execute files in
<mydocroot>/components by just specifying their name, without
directory. This works perfectly well as long as my base document
(base.epo) cannot be found in the normal hierarchie of
directories but only in that components directory. Example:
In <mydocroot>/home/index.epo I want to Execute
<mydocroot>/components/logo.epo by just typing
Execute ('logo.epo');
If either <mydocroot>/base.epo or <mydocroot>/home/base.epo exist
this does not work. If I move <mydocroot>/base.epo to
<mydocroot>/components/base.epo everything is ok.
As I understand it in EmbperlObject.pm, line 206ff $searchpath is
extended by paths from $ENV{EMBPERL_OBJECT_ADDPATH} _only_ when
$basename is _not_ found earlier, while processing the directory
hierarchie from dirname($req -> {inputfile}) down to
$stopdir and the likes.
I verified this behaviour by creating a <mydocroot>/temp/base.epo
which tries to Execute header.epo, * and footer.epo and
a corresponding <mydocroot>/temp/index.epo which I tryed to
request. As I expected header.epo and footer.epo could not be
found despite they exist in <mydocroot>/
If this behaviour is intended I would be happy to know why...
Andre
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
