Tod Harter wrote:
That's a common artefact of using Apache::Reload or Apache::StatINC, and the behaviour you describe could indeed be what's happening here, I've seen it myself. The reason for this is (I think) that those modules use evals (thus the server doesn't crash upon error) and that once they've failed to load a module once, they'll leave it out and won't ever reload it.On Monday 21 October 2002 05:06 am, Robin Berjon wrote: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...Todd W wrote:( 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?
While on the topic, I'd recommend Apache::Reload over Apache::StatINC, especially as you'll need it if you want your "Certified 100% Pure MSERGEANT Solution Provider" label.
--
Robin Berjon <[EMAIL PROTECTED]>
Research Engineer, Expway
7FC0 6F5F D864 EFB8 08CE 8E74 58E6 D5DB 4889 2488
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
