On Monday 21 October 2002 05:06 am, Robin Berjon wrote: > Todd W wrote: > > When I point my browser to ANY uri that is prossed by AxKit, I get a > > server 500 error and the following in error_log: > > > > [Sun Oct 20 23:20:23 2002] [error] [client 127.0.0.1] [AxKit] [Error] > > Can't locate object method "register" via package "My::WeatherTaglib" > > (perhaps you forgot to load "My::WeatherTaglib"?) at > > /usr/lib/perl5/site_perl/5.6.1/i686-linux/Apache/AxKit/Language/XSP.pm > > line 168. > > > > When I comment out "AxAddXSPTaglib My::WeatherTaglib" the browser gets a > > document without the weather information and I can get content (instead > > of the 500 error) for other resources processed by AxKit (i.e. > > http://localhost/xsp/time.xsp from the previous article). > > > > The module is definitely loaded because I have a perl handler mapped to > > a uri that dumps the @inc array and the keys and values of the %INC hash > > ( I use Apache::StatINC ). > > It looks as if My::WeatherTaglib is not inheriting from > Apache::AxKit::Language::XSP like it should. If you add that does it work? The other possibility which I've seen is that in certain circumstances (and I am not sure why, I never really investigated too much) a Taglib can fail to compile for any old ordinary reason like some other module it uses is missing, and AxKit/mod_perl will happily go right along and do its thing with no visible sign of error until you try to serve the page in question. Then you get something like this message about not being able to register, just as if the taglib had never loaded. Where did the error message go? Who knows...
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
