>
> Could you just rely on the manager application to reload the webapp?
> Then there is no code to maintain.
>
I've been looking for an effective way to emulate the unix 'kill -HUP'
command for ages. It's not always practical to kill off the webapp, since
you need to ensure that no-one is usin
If your using apache - a good admin will be able to sufficently protect
the manager webapp.
The ServletContext is always available.
From servlets:
ServletContext myContext= this.getServletConfig().getServletContext();
From JSP:
Provided via the "application" scripting variable.
Felipe Schnack
yes.. synch is really a pain!
but what you mean you mean set ServletContext.setAttribute()? This
isn't only visible in all instances of a specific servlet?
My problem with manager is that a sysadmin here don't like the idea of
have such an adminastive tool open to the web... i don't agree wi
Could you just rely on the manager application to reload the webapp?
Then there is no code to maintain.
Otherwise - your in a kludge. You can:
- Put a "status" object in your application context
- When a servlet is executed - it can first check its "status" instance
locally stored against the ap
