Hi Filip,
I'm only responding to the loader naming bit in this message (I
need to think about the session management stuff a little bit more still).
So I think I see the changes in tomcat trunk to support loader
names. There is a new interface
(org.apache.catalina.loader.NamedClassLoader) which the tomcat loaders
implements and the various bits of code that construct those loaders take
care of assigning the names.
For use in Terracotta, we'll still need to take care of adapting
to our own NamedClassLoader interface and registering the loaders with our
loader repository. That said, it's great that we can now rip out some of
our code (for tomcat 6 at least)
Out of curiosity, are there any other uses cases that prompted the
addition of the loader names (besides Terracotta)? The whole business of
naming loaders is something I would love to an alternate solution for, and
perhaps looking at some other contexts would help crack that nut
-tim
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:tc-dev-
> [EMAIL PROTECTED] On Behalf Of Filip Hanik - Dev Lists
> Sent: Friday, August 17, 2007 2:59 PM
> To: TC-DEV
> Subject: [tc-dev] named classloaders in Tomcat
>
> Hi all,
> In Tomcat 6.x (trunk) we have added in names to all the classloaders in
> Tomcat
> Names are
> common
> shared
> server
> For the top level loaders.
>
> And for the webapp classloaders, the name is
> Engine.name#Host.name#Context.name
>
> For example
> Catalina#localhost#/probe
>
> And for the ROOT context, it would be
> Catalina#localhost#
>
> Since the name of that context is ""
_______________________________________________
tc-dev mailing list
[email protected]
http://lists.terracotta.org/mailman/listinfo/tc-dev
