Why can't the httpsession clustering be conditional on the existence of the <distributable> web.xml tag so that the jbossha-httpsession.sar can be deployed as part of the all configuration?
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Sacha Labourey" <[EMAIL PROTECTED]> To: "Scott M Stark" <[EMAIL PROTECTED]> Sent: Saturday, August 10, 2002 2:13 AM Subject: RE: jbossha-httpsession.sar location > Yes. When you deploy cluster-service.xml in server/all/deploy, beans are not > automatically clustered (you need to modify jboss.xml) which is good because > people may get strange behaviour if they don't think properly about what > they do. > > But things are different for jbossha-httpsession.sar: if you deploy it, all > web-apps httpsessions are automatically clustered, without having to > configure anything. this can also be dangerous (and lead to e-mails on > jboss-dev) => it is in another place. > > BUT! I agree that it is not the best place we could imagine. > > If you think it is wrong, change it: you're the chief. > > Cheers, > > > Sacha > > > > > -----Message d'origine----- > > De : Scott M Stark [mailto:[EMAIL PROTECTED]] > > Envoyé : vendredi, 9 août 2002 22:46 > > À : Sacha Labourey > > Objet : jbossha-httpsession.sar location > > > > > > Is there a reason jbossha-httpsession.sar was placed into > > docs/examples/clustering instead of server/all/deploy? > > > > > > > > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
