Jon Stevens has proposed a patch to change the event order during the
process of a context reload (either because a modified class was detected
when you set reloadable to true, or manually via the Manager webapp).
Here's the current event order (in StandardContext.reload()):
(1) Pause requests
on 9/20/01 2:21 PM, Craig R. McClanahan [EMAIL PROTECTED] wrote:
I cannot see that this would cause any difficulties with dependencies.
Can anyone else see a problem with it?
Craig McClanahan
+1
I'm ok with the filters being initialized first since I'm not using any. :-)
Thanks for the
