The only thing the "clustered-jetty" terracotta config module does [currently] is take care of naming and registering classloaders.
The clustered session support for Jetty does not use the Terracotta session implementation (thus it does not use the <web-applications> section of tc-config.xml). It only relies on the Terracotta ManagerUtil API to get roots and locks, the rest is jetty code. There is definitely more we could do with making the session support a little more drop-in, but it is not done (as you noticed). Doing the class export and activation of the clustered session manager from the jetty config module would go a long way probably. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:tc-dev- > [EMAIL PROTECTED] On Behalf Of Eugene Kuleshov > Sent: Wednesday, October 03, 2007 9:05 AM > To: [email protected] > Cc: Jan Bartel > Subject: [tc-dev] jetty integration for Terracotta > > > I've been looking at configuring Jetty support for Terracotta plugin > for Maven [1] and found current Jetty configuration for Terracotta [2] > quite confusing. > > First of all that documentation at the Codehaus is outdated. It says > that user need to install terracotta jars, but actual pom.xml from > Jetty's svn is trying to download it from the Terracotta's Maven > repository, but it is using wrong url. > > Then it is weird that Jetty require some special configuration for > Terracotta clustering. There is a config module shipped with the > Terracotta kit (and also can be downloaded from the Terracotta's Maven > repository), then there is a separate jar that need to be built manually > and copied somewhere inside jetty folders. More over, that integration > seem to ignore info from the Terracotta config that specify which web > applications need to be clustered and instead user is expected to > manually edit deployment descriptors for each web application that need > to be clustered. > > With these issues it is practically difficult to use Jetty from our > clustered Cargo support for Maven (i.e. for the integration testing). I > wonder if there are plans to somehow address these issues? > > I think it need to be simplified, so user could just specify jetty > config module in tc-config.xml (or using newly introduced properties > like Gary just explained in his yesterday's email). Then that module > should use settings about clustered web applications from tc-config.xml > and automatically activate all necessary configuration in deployment > descriptors. More over, that config module should also export all > required classes, so user don't have to build and copy any additional > jars. We have this stuff working for other web application servers and > frameworks (Tomcat, WebLogic, RIFE) and it should be straightforward to > do the same for Jetty and will make configuration efforts for Terracotta > for Jetty close to none. > > regards, > Eugene > > [1] > http://www.terracotta.org/confluence/display/wiki/Terracotta+Maven+Plugin > [2] > http://docs.codehaus.org/display/JETTY/Session+Clustering+with+Terracotta > > > _______________________________________________ > tc-dev mailing list > [email protected] > http://lists.terracotta.org/mailman/listinfo/tc-dev _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
