Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 17227 invoked from network); 1 Nov 2006 18:46:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Nov 2006 18:46:35 -0000 Received: (qmail 79437 invoked by uid 500); 1 Nov 2006 18:46:32 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 79240 invoked by uid 500); 1 Nov 2006 18:46:32 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 79229 invoked by uid 99); 1 Nov 2006 18:46:32 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Nov 2006 10:46:32 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [195.227.30.246] (HELO datura.kippdata.de) (195.227.30.246) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Nov 2006 10:46:18 -0800 Received: from [192.168.2.123] ([192.168.2.123]) by datura.kippdata.de (8.13.5/8.13.5) with ESMTP id kA1Ijrot010157 for ; Wed, 1 Nov 2006 19:45:54 +0100 (CET) Message-ID: <4548EB61.2040000@kippdata.de> Date: Wed, 01 Nov 2006 19:45:53 +0100 From: Rainer Jung User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Tomcat Users List Subject: Re: Webapps that run on 5.0.28 but not 5.5.x? References: <4548E0D9.7090803@apache.org> In-Reply-To: <4548E0D9.7090803@apache.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Apart from the changes in suggested deployment strategies and ressourec definitions there's something to be careful: Upgrading to TC 5.5 and upgrading from Java 1.4 to Java 5 are two different things. As long as you do only the first, chances are good, that you get the webapp to run without code changes. An upgrade to Java 5 should be tried only after you get the webapp to run under TC 5.5 with Java 1.4. Regards, Rainer Glen Mazza schrieb: > Hello, > > Question: How common is it for a webapp to be able to run on Tomcat > 5.0.28 but *not* 5.5.20? > > For the installation of a commerical web application that calls for > installation of Tomcat 5.0.28, I'm inclined to just go ahead and use the > 5.5 series of servlet containers. Customer support is concerned that > Tomcat 5.5 will not work (or at least has not been tested on the new > version). My thinking is that: > > 1.) Both containers implement the same specifications, so their > development team would *really* have to be coding obscurely, bending > over backwards to try to trip up the 5.5 servlet container, to be able > to manage to build a webapp that will run on 5.0.28 but not 5.5.20. > > 2.) Further, it would require an extremely talented development team to > be able to create a webapp that will run on 5.0.28 but not 5.5.20, but > paradoxically, if they had that level of talent they would *not* build > an application anyway that will work on 5.0.28 but not 5.5.20. > > Is my logic here correct or faulty? To what degree is "This webapp will > work on 5.0.28 but not 5.5.20" an old wives' tale? > > Thanks, > Glen > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org > For additional commands, e-mail: users-help@tomcat.apache.org --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org