Re: Howto develop with modperl 2 ? (Restart Apache all the time ?)

[Jens Helweg]

That's what I've tried and how I determined that the reload does not 
seem to work.
When I change something in my perl module it still doesn't take effect. 
Only when I restart Apache the changes apply.

Now I'd wish to verify that the monitoring of my perl module is really 
done by the reload module. Maybe it's possible to log some of the things 
the reload module does ?


Lionel MARTIN wrote:
Yes, easily.

In any of your handler, you make a reference to one test module.

For example, in your response handler:

use myModule();
use Apache2::Const -compile => qw(OK);
sub handler {
  myModule::printHello();
  return Apache2::Const::OK;
}
1;

And then: myModule.pm:

sub printHello {
  print 'Hello';
}
1;

Then, you start your server, and test your handler.
It should print 'Hello';

Then, without restarting your server, you change myModule.pm into:

sub printHello {
  print 'Hi';
}
1;

And you run your page again.

This time, it should print 'Hi', showing that Apache took the update 
into account on the fly, without having to restart anything.

HTH.

Lionel.

----- Original Message ----- From: "Jens Helweg" <[EMAIL PROTECTED]>
To: <modperl@perl.apache.org>
Sent: Thursday, June 21, 2007 11:12 AM
Subject: Re: Howto develop with modperl 2 ? (Restart Apache all the time ?)


Thank you. I really missed the second ':'.
Now it's not complaining anymore but the reload still doesn't work...

Is there a way to verify that the Reload module has been loaded and 
that is works at all ?


Sean Davis wrote:
Jens Helweg wrote:
Thanks Linonel, Jonathan.
I have added this to my configuration and now get the error message:

failed to resolve handler `Apache2:Reload':

I haven't had the chance to look at this any closer. I will do this
tomorrow, though. I don't want to overstrain your help - but do you 
have
an idea ?

Is this error cut-and-paste?  If so, you have only one ':'.

Sean