> > 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 using it at the time. > 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. > You may be able to minimise the synchronization effect by adapting the technique used by the "fast collections" implemented in the Apache Commons project. These allow unsynched read access unless a change is taking place, in which case the read access is only synced until the change is finished. Regards Roger -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
