On Tue, 2003-09-16 at 12:48, Matt Sergeant wrote:
> On 16 Sep 2003, at 20:11, Arne Claassen wrote:
> 
> > On Tue, 2003-09-16 at 11:34, Matt Sergeant wrote:
> >> Don't use <?xml-stylesheet?> - if you do that you have no control over
> >> the sort of things you want to do.
> >>
> >> Instead use AxAdd*Processor directives. This will do what you want.
> >
> > Ok.. Trying to use AxAddDynamicProcessor. But i presume this happens
> > post URI stage, so I have to have a separate handler to parse the URI
> > first, then catch it with the processor and do the stylesheet stuff. I
> > was going to try that using $r->pnotes to make a note to myself whether
> > this started out as .xml or .html but i can't see $r being availavle to
> > AxAddDynamicProcessor. Am i missing something else?
> 
> You can get it via Apache->request().

Ok, now i'm just down what's likely a to stupid perl errors, but i sure
can't figure it out. Created a Processor, simply called Processors.pm. I
can require it in a test script and everything is fine, so i don't think
i have a namespace issue. But as soon as i put it in as a
AxAddDynamicProcessor and try to hit a page that invokes it, i get this
in my logs:

[Tue Sep 16 16:08:32 2003] [error] [client 172.20.2.242] [AxKit] [Error]
AxKit::load_module failed: Can't locate Processors.pm in @INC (@INC
contains: /home/arne/scripts /www/lib
/usr/lib/perl5/5.8.0/i386-linux-thread-multi /usr/lib/perl5/5.8.0
/usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.0 /usr/lib/perl5/site_perl
/usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.0 /usr/lib/perl5/vendor_perl .
/usr/local/apache-1.3.28+mod_ssl+mod_perl+mod_gzip/
/usr/local/apache-1.3.28+mod_ssl+mod_perl+mod_gzip/lib/perl) at (eval
4796) line 1.

I have a PerlRequire in my httpd.conf doc, plus it's in
/home/arne/scripts anyhow.

Anyone?

arne


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to