Hi Eugene,
> 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.
Regarding the wiki instructions, you're quite right that one no longer
needs to install the terracotta jar because you've now made your jars
available on a maven repo. I've removed those lines from the instructions.
Thanks for pointing that out. Things change very rapidly and it's always
hard to make sure the documentation keeps pace.
The repo url is the one Taylor gave me about a month ago:
<repository>
<id>terracotta.org</id>
<url>http://download.terracotta.org/maven2-snapshots/</url>
</repository>
If it has changed, please let me know and I will update the jetty
build (FYI we are about to do a 6.1.6r0 release, so if you can let
me know ASAP I may be able to squeeze that in).
> 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)
I don't pretend to be a terracotta expert by any means - the config file
that we have checked in to jetty is AFAIK essential to making tc work
with the jetty module. It certainly was when we started development of
the tc/jetty integration (before there even _was_ a jetty module).
However, as you guys have done more work, then maybe these days it
is superfluous - please just let me know or point me at your most
recent documentation and I'll update jetty and docs accordingly.
> then there is a separate jar that need to be built manually
> and copied somewhere inside jetty folders.
Yeah, that's right. Before terracotta was mavenized, we obviously could
not automatically build the tc/jetty integration. Now that you are mavenized,
this is possible, and therefore we could also copy the tc integration
jar to jetty lib/ext as part of the build.
> 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.
I think you're asking a more general question, like why doesn't jetty
reuse more of the existing terracotta session handling code. The
answer is that at the time we embarked on this, that code had quite
a tomcat flavour and would have been difficult to apply to jetty. Also,
jetty has some very specific session handling code that we have honed
over a number years to take account of the vagaries of the servlet
spec, so we would have been/are very loath to throw that out.
The configuration of the webapps that you refer to is a standard way
of configuring things for jetty users. We have pluggable SessionManagers
and SessionIdManagers, and different implementations for different
clustering technologies. It could be interesting if the plugging
could be done automatically based on the <webapp> elements in
the tc config file.
> 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.
I'm not entirely sure what you're proposing here - probably due to my
lack of knowledge of recent developments in terracotta. Are you suggesting
to move the integration code that we maintain in the jetty repo over
into the terracotta repo where it could become part of the "clustered-jetty"
module and therefore part of the tc distro?
cheers
Jan
_______________________________________________
tc-dev mailing list
[email protected]
http://lists.terracotta.org/mailman/listinfo/tc-dev
