The ServletContext is always available.
From servlets:
ServletContext myContext= this.getServletConfig().getServletContext();
From JSP:
Provided via the "application" scripting variable.
Felipe Schnack wrote:
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 with him, but what can i do? :-)On Wed, 2002-11-20 at 11:22, Tim Funk wrote: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 application version. If out of sync - the servlet can reload its config. But this requires a syncronization block on the servlet which is a pain.
IMO - Use the manager app.
Felipe Schnack wrote:
I have a servlet mapped to a specific url, let's say "/reset". When this URL is accessed, I would like this servlet to notify all instances of another one that they should reload their configuration data. How can I do that?-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
