Guys,
Jan and I have just refactored the Geronimo Jetty and Tomcat
integrations to take the same approach to the installation of a 3rd
party session manager, to ease the integration of WADI. This is now
checked in on Geronimo's trunk.
Each top level web container GBean now supports a pair of attributes -
LocalSessionManager and DistributableSessionManager. These may be used
to override the container's choice of SessionManager for webapps with
and without the <distributable/> tag present in the WEB-INF/web.xml,
respectively.
The attributes expect to be given a classname, if required, this class
will be loaded and instantiated. The resulting instance will be used as
the session manager. If not provided, the container will use a sensible
default. Currently Jetty and TC are set up to use their own default
session managers in the local case and the correct WADI session manager
in the distributable case.
This means that the same WADI-enabled webapp, with its plan held
internally (WEB-INF/geronimo-web.xml) may now be hot-deployed on either
a Jetty or a Tomcat based Geronimo, without changes :-)
I will post specific WADI issues to the WADI dev lists
([email protected], [EMAIL PROTECTED]).
This shouldn't be seen as a final position on the subject - there is
still much to talk about, but is a useful interim step, that allows us
to have something working whilst we figure out how to go forward.
Enjoy,
Jules
--
"Open Source is a self-assembling organism. You dangle a piece of
string into a super-saturated solution and a whole operating-system
crystallises out around it."
/**********************************
* Jules Gosnell
* Partner
* Core Developers Network (Europe)
*
* www.coredevelopers.net
*
* Open Source Training & Support.
**********************************/
