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]>
