I'm curious, do you need anything in server.xml ? +1 on making it a module, as independent of tomcat version ( or tomcat in general ) as possible. Add any hooks you need to avoid strong dependencies. I think the connectors worked pretty well as a version-independent tomcat module.
I think it would be even better if the clustering modules would be released independently of tomcat - i.e. as an add-on module, in a separate download, with it's own config file ( the 'trusted webapps' have access to internal classes - so it can be even packaged as a .war :-). Costin On 2/23/06, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote: > Sounds like there is a consensus amongst folks. So to summarize > everyones thoughts, let me know if this sounds like a solution agreeable > to everyone. > > 1. Keep 5.5.x as a maintenance module as it was of 5.5.15 + cross context > > 2. Break out cluster config from catalina.jar to catalina-cluster.jar > that way we can enable more than one config > In Catalina.java have a ClusterRuleSetFactory.getClusterRuleSet() > that will load the rule set run time. > > 3. Create two new modules (to use for TC6 and as an optional library for > TC 5.5.x) > a) Name:groupcom > Lib : catalina-groups.jar > Purpose: Group messaging component > b) Name: ha > Lib : catalina-cluster.jar > Purpose: session replication logic, context attribute replication > and other new features > > > Lets gather one round of feedback and then vote so that I can move on > with new dev. > > Filip > > > > > > --------------------------------------------------------------------- > 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]
