is there an event that gets fired after the contexts have been configured, but before the connectors start accepting requests?
I need this event so that I can replicate session data for a new node that joins the cluster, and we don't want to start accepting requests until we are complete with that one. Filip -----Original Message----- From: Costin Manolache [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 26, 2003 1:48 PM To: [EMAIL PROTECTED] Subject: Re: commons-modeler in jtc and catalina Jeanfrancois Arcand wrote: > Costin, > > are you planning to tag the modeler workspace to reflect all you recent > changes (once they are completed of course)? Something like > MODELER_2_0_alpha (I'm not good for name) will be helpfull. Also, is > this module supposed to build by itself? Right now the build.xml has a > dependency on jakarta-commons. Bundling Tomcat 5 source creates huge zip > file (>50mg) mostly due to jakarta-commons source dependency. If the > dependency is not required, I would be happy to help fixing the > build.xml.. It wouldn't be bad if the source zip would include the commons code that we use - modeler, logging, digester, beanutils, collections. But you can fix it to include only tomcat-specific code, since commons has its own src distribution. I don't know if you follow the discussion on the repository - it'll probably affect us a lot. If things settle down and an agreement is reached - we should modify our build acordingly. That may mean we'll have to include version numbers in jars ( if this is voted ), start downloading and uploading to the repository, etc. Probably the some of the download script could be replaced with ruper or some other task ( I hope Ant1.6 will include such a thing by default ). Regarding the tag - I think it would be a good idea to tag it with each milestone of tomcat5. BTW - in order to release modeler we need at least 3 +1 votes - so far I feel a bit alone :-) Is anyone else interested in this piece ? Costin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]