Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 57242 invoked from network); 25 Jan 2006 14:51:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 25 Jan 2006 14:51:23 -0000 Received: (qmail 1900 invoked by uid 500); 25 Jan 2006 14:51:20 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 1829 invoked by uid 500); 25 Jan 2006 14:51:20 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 1811 invoked by uid 99); 25 Jan 2006 14:51:20 -0000 X-ASF-Spam-Status: No, hits=-10.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [209.237.227.194] (HELO [127.0.0.1]) (209.237.227.194) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Jan 2006 06:51:18 -0800 Message-ID: <43D79102.7010107@apache.org> Date: Wed, 25 Jan 2006 15:53:54 +0100 From: Carsten Ziegeler User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: Update to the Servlet API References: <20060123103342.GB72971@vision.anyware> <43D4BC59.8060203@apache.org> <20060125120514.GH56365@vision.anyware> <43D76C99.1010506@apache.org> <43D78D24.9020503@apache.org> In-Reply-To: <43D78D24.9020503@apache.org> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Sylvain Wallez wrote: > Carsten Ziegeler wrote: >> Jean-Baptiste Quenot schrieb: >> >>> I wish to replace servlet_2_2.jar with servlet_2_3.jar, but keep >>> compatibility with servlet 2.2, by making servlet2.3-requiring >>> components optional. >>> >> You can't check if a component uses 2.3 functionality, so if we just >> upgrade we might end up with a not 2.2 servlet compliant solution. (Or >> is there a way?) >> > > Servlet 2.3 has been released more than 4 years ago[1]. IMO it is safe > to consider that people using recent versions of Cocoon are running at > least servlet 2.3 and most probably servlet 2.4. > > So depending on servlet 2.3 shouldn't be that much of a problem. > Yes, that's why I said in an earlier response that we can vote on upgrading the requirements to servlet 2.3 officially. Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/