I also had to make the follow addition to my config file:
PerlInitHandler Apache2::Reload
PerlSetVar ReloadAll Off
I never figured out how to check if it was actually picking up changes on its
own.
For now, I have reverted to not using Apache2::Reload, which is kind of a shame
since I am still in the development stages of my application.
greanie
----- Original Message ----
From: Jonathan Vanasco <[EMAIL PROTECTED]>
To: modperl mod_perl <modperl@perl.apache.org>
Sent: Wednesday, October 18, 2006 3:00:43 PM
Subject: Re: apache2::reload causing 500 errors on return statement
On Oct 18, 2006, at 10:59 AM, Michael Greenish wrote:
> Hello,
>
> I just added apache2::reload to config & handlers, classes,
> packages for my application. However, everywhere I have "return
> OK", I get an error:
>
> "Not a CODE reference at /http/greanie/IndexHandler.pm on ..."
>
> and request returns the page and a 500 error (in browser, I see
> rendered page plus 500 error at bottom). Can I not use
> Apache2::Reload in the handler?
i've never had that issue...
but i just did a check on the Apache2::Reload, and it seems to not
pick up any changes I make to the handler. I never noticed that
before ( i tend to just use it to dispatch to other modules)
tried it on osx, ubuntu and freebsd - same results.
