Moving from Tomcat 5 to Tomcat 6

[Tim Ruppert]

All, I just wanted to check and see if anyone has attempted to bring  
Tomcat 5 up to Tomcat 6?  Please let me know if you have.

In general, what are everyone's thoughts on making a move like this?  
Is there anyone else out there who might benefit from having a 2.4  
servlet container in there?  Let me know.

Cheers,
Tim
--
Tim Ruppert
HotWax Media
http://www.hotwaxmedia.com

o:801.649.6594
f:801.649.6595

[Joe Eckard]

I haven't tried updating Tomcat, but I did update the JettyContainer  
to use jetty 6 (Servlet 2.5 / JSP 2.1) and I've been running it in  
production with no problems.

Just out of curiosity, what were the reasons for switching the default  
servlet container from Jetty to Tomcat a few years ago? Maybe those  
features are in Jetty now, or issues have been fixed? I have no real  
preference either way at this time, I was just wondering.

-Joe

On May 19, 2008, at 2:20 PM, Tim Ruppert wrote:

> All, I just wanted to check and see if anyone has attempted to bring  
> Tomcat 5 up to Tomcat 6?  Please let me know if you have.
>
> In general, what are everyone's thoughts on making a move like  
> this?  Is there anyone else out there who might benefit from having  
> a 2.4 servlet container in there?  Let me know.
>
> Cheers,
> Tim
> --
> Tim Ruppert
> HotWax Media
> http://www.hotwaxmedia.com
>
> o:801.649.6594
> f:801.649.6595
>
>

[David E Jones]

It's been a few years since we made the switch, so Jetty may have  
caught up in that time. During that switch the biggest issue was that  
Jetty only supported session replication (for fail-over purposes) if  
run with JBoss, and Tomcat had a much better/cleaner implementation  
that didn't require JBoss. I'm guessing they've changed that by now...

Jetty was also minimally maintained for a few years, so there was no  
reason to consider changing back.

At this point I'd rather stick with Tomcat as the default, partly  
because of popularity and partly because it is an ASF project. Of  
course, if Jetty offers features that Tomcat doesn't at this point and  
we like those, we should go for it and if the Tomcat guys notice maybe  
it'll help them out with a "real world" case that could be interesting.

Either way, since there are two good containers I like the idea of  
supporting both so that people can choose what they want to use.

-David


On May 19, 2008, at 1:39 PM, Joe Eckard wrote:

> I haven't tried updating Tomcat, but I did update the JettyContainer  
> to use jetty 6 (Servlet 2.5 / JSP 2.1) and I've been running it in  
> production with no problems.
>
> Just out of curiosity, what were the reasons for switching the  
> default servlet container from Jetty to Tomcat a few years ago?  
> Maybe those features are in Jetty now, or issues have been fixed? I  
> have no real preference either way at this time, I was just wondering.
>
> -Joe
>
> On May 19, 2008, at 2:20 PM, Tim Ruppert wrote:
>
>> All, I just wanted to check and see if anyone has attempted to  
>> bring Tomcat 5 up to Tomcat 6?  Please let me know if you have.
>>
>> In general, what are everyone's thoughts on making a move like  
>> this?  Is there anyone else out there who might benefit from having  
>> a 2.4 servlet container in there?  Let me know.
>>
>> Cheers,
>> Tim
>> --
>> Tim Ruppert
>> HotWax Media
>> http://www.hotwaxmedia.com
>>
>> o:801.649.6594
>> f:801.649.6595
>>
>>
>

[Jacques Le Roux]

There are also both available in Geronimo (or IBM WASCE)

Jacques

From: "David E Jones" <[hidden email]>

>
> It's been a few years since we made the switch, so Jetty may have  
> caught up in that time. During that switch the biggest issue was that  
> Jetty only supported session replication (for fail-over purposes) if  
> run with JBoss, and Tomcat had a much better/cleaner implementation  
> that didn't require JBoss. I'm guessing they've changed that by now...
>
> Jetty was also minimally maintained for a few years, so there was no  
> reason to consider changing back.
>
> At this point I'd rather stick with Tomcat as the default, partly  
> because of popularity and partly because it is an ASF project. Of  
> course, if Jetty offers features that Tomcat doesn't at this point and  
> we like those, we should go for it and if the Tomcat guys notice maybe  
> it'll help them out with a "real world" case that could be interesting.
>
> Either way, since there are two good containers I like the idea of  
> supporting both so that people can choose what they want to use.
>
> -David
>
>
> On May 19, 2008, at 1:39 PM, Joe Eckard wrote:
>
>> I haven't tried updating Tomcat, but I did update the JettyContainer  
>> to use jetty 6 (Servlet 2.5 / JSP 2.1) and I've been running it in  
>> production with no problems.
>>
>> Just out of curiosity, what were the reasons for switching the  
>> default servlet container from Jetty to Tomcat a few years ago?  
>> Maybe those features are in Jetty now, or issues have been fixed? I  
>> have no real preference either way at this time, I was just wondering.
>>
>> -Joe
>>
>> On May 19, 2008, at 2:20 PM, Tim Ruppert wrote:
>>
>>> All, I just wanted to check and see if anyone has attempted to  
>>> bring Tomcat 5 up to Tomcat 6?  Please let me know if you have.
>>>
>>> In general, what are everyone's thoughts on making a move like  
>>> this?  Is there anyone else out there who might benefit from having  
>>> a 2.4 servlet container in there?  Let me know.
>>>
>>> Cheers,
>>> Tim
>>> --
>>> Tim Ruppert
>>> HotWax Media
>>> http://www.hotwaxmedia.com
>>>
>>> o:801.649.6594
>>> f:801.649.6595
>>>
>>>
>>
>

[Jacopo Cappellato-3]

Hi all,

I have created a new Jira issue and I have submitted a patch to  
migrate to Tomcat 6:

https://issues.apache.org/jira/browse/OFBIZ-1800

I'm testing it right now, but your reviews and comments would be very  
much appreciated.

Jacopo


On May 20, 2008, at 8:21 AM, Jacques Le Roux wrote:

> There are also both available in Geronimo (or IBM WASCE)
>
> Jacques
>
> From: "David E Jones" <[hidden email]>
>> It's been a few years since we made the switch, so Jetty may have  
>> caught up in that time. During that switch the biggest issue was  
>> that  Jetty only supported session replication (for fail-over  
>> purposes) if  run with JBoss, and Tomcat had a much better/cleaner  
>> implementation  that didn't require JBoss. I'm guessing they've  
>> changed that by now...
>> Jetty was also minimally maintained for a few years, so there was  
>> no  reason to consider changing back.
>> At this point I'd rather stick with Tomcat as the default, partly  
>> because of popularity and partly because it is an ASF project. Of  
>> course, if Jetty offers features that Tomcat doesn't at this point  
>> and  we like those, we should go for it and if the Tomcat guys  
>> notice maybe  it'll help them out with a "real world" case that  
>> could be interesting.
>> Either way, since there are two good containers I like the idea of  
>> supporting both so that people can choose what they want to use.
>> -David
>> On May 19, 2008, at 1:39 PM, Joe Eckard wrote:
>>> I haven't tried updating Tomcat, but I did update the  
>>> JettyContainer  to use jetty 6 (Servlet 2.5 / JSP 2.1) and I've  
>>> been running it in  production with no problems.
>>>
>>> Just out of curiosity, what were the reasons for switching the  
>>> default servlet container from Jetty to Tomcat a few years ago?  
>>> Maybe those features are in Jetty now, or issues have been fixed?  
>>> I  have no real preference either way at this time, I was just  
>>> wondering.
>>>
>>> -Joe
>>>
>>> On May 19, 2008, at 2:20 PM, Tim Ruppert wrote:
>>>
>>>> All, I just wanted to check and see if anyone has attempted to  
>>>> bring Tomcat 5 up to Tomcat 6?  Please let me know if you have.
>>>>
>>>> In general, what are everyone's thoughts on making a move like  
>>>> this?  Is there anyone else out there who might benefit from  
>>>> having  a 2.4 servlet container in there?  Let me know.
>>>>
>>>> Cheers,
>>>> Tim
>>>> --
>>>> Tim Ruppert
>>>> HotWax Media
>>>> http://www.hotwaxmedia.com
>>>>
>>>> o:801.649.6594
>>>> f:801.649.6595
>>>>
>>>>
>>>
>>