I don't have the history to answer your last question ... perhaps somebody else can.

As to what is Jetty specific in the console .... it may be not as bad as I think it is ....(I'm just now about to configure tomcat and see what happens). 
However, as I look in the code for the web server and connection management I see many instances where special processing is done for Jetty but not Tomcat.   Perhaps none is necessary for Tomcat? 
There is a log viewer portlet that is Jetty Specific and I don't see another equivalent for Tomcat.
Other posts have indicated problems with the console and tomcat ... but they may have already been fixed.   I'll find out soon :-)  .

Joe


Bruce Snyder wrote:
On 8/26/05, Joe Bohn <[EMAIL PROTECTED]> wrote:

  
 Of course this is required in Geronimo R1 .... and I think it is also
required in M5.     
 
 However, based upon some of the comments around certification of Tomcat, I
thought I should ask if everyone felt that this was necessary for M5. 
    

Thanks for the clarification, Joe. Now I understand that your comments
are aimed at M5 only. That being said, what exactly is missing? And
why was the choice made to develop the console in such a Jetty
specific manner?

Bruce 
  

-- 
Joe Bohn     
[EMAIL PROTECTED]

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

Reply via email to