geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Bohn <>
Subject Re: How do we ship jetty and tomcat versions? Please respond
Date Tue, 06 Sep 2005 13:26:38 GMT
I too am confused about the use case scenario that would drive this?   
Also, can we be more specific on the level of granularity that is being 
considered here?  Would it be just: 1 tomcat container,  1 jetty 
container, both a single tomcat and a single jetty container?   Or is it 
also being considered that we would support multiple tomcat containers 
and multiple jetty containers (possibly even at different container 

Do any other application servers support multiple concurrent web 

If it is decided that this is a valid scenario, then the implications of 
this would ripple throughout the code.  This is especially problematic 
for the web console where we would have to visually keep track of 
multiple containers, applications, connections, etc.. active on each 
container, logs associated with each container, configuration attributes 
of each container, etc... But I think this approach would have 
significant implications for other components as well, including 3rd 
party software that might need to interact with our server (such as 
external management applications using JMX).


Jacek Laskowski wrote:

> David Jencks wrote:
> ...
>> I wrote a namespace-driven switching module builder to determine if 
>> the jetty or tomcat builder is used.  It has a defaultNamespace  
>> option which is what currently determines the target.  The module 
>> builders register themselves with the switch and supply their namespace.
> ...
>> So, in more detail, I propose we ship:
>> -all the configurations, for both jetty and tomcat, installed
>> - 3 pairs of config.list and config.xml files that run both, only 
>> jetty, and only tomcat
>> - both containers and builders running by default.
> Hi Dave,
> Both, by default? Interesting. Will there be a way in your proposal to 
> deploy a WAR to *both* containers? Since the defaultNamespace option 
> is to drive what container a WAR is deployed to I think the answer is 
> negative, isn't it? (or alternatively it could assume that no 
> defaultNamespace would mean both) If so, why would a user want to run 
> Jetty and Tomcat? I don't mind having two containers and builders 
> running at the same time, but wonder if there's a user case for it (a 
> web hosting provider?).
>> david jencks
> Jacek

Joe Bohn

"He is no fool who gives what he cannot keep, to gain what he cannot lose."   -- Jim Elliot

View raw message