Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 76324 invoked from network); 4 May 2004 21:23:28 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 4 May 2004 21:23:28 -0000 Received: (qmail 27406 invoked by uid 500); 4 May 2004 21:23:12 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 27355 invoked by uid 500); 4 May 2004 21:23:11 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 27337 invoked from network); 4 May 2004 21:23:11 -0000 Received: from unknown (HELO web50608.mail.yahoo.com) (206.190.38.95) by daedalus.apache.org with SMTP; 4 May 2004 21:23:11 -0000 Message-ID: <20040504212317.40413.qmail@web50608.mail.yahoo.com> Received: from [66.80.49.7] by web50608.mail.yahoo.com via HTTP; Tue, 04 May 2004 14:23:17 PDT Date: Tue, 4 May 2004 14:23:17 -0700 (PDT) From: David Graham Subject: Re: [digester] local ArrayStack implementation not backwardscompatible? To: Jakarta Commons Developers List In-Reply-To: <5027A226-9E0F-11D8-ABE2-003065DC754C@blueyonder.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N --- robert burrell donkin wrote: > On 24 Apr 2004, at 04:19, Craig R. McClanahan wrote: > > > > > From what I can see on TOMCAT-DEV, the Tomcat developers think that > > there are backwards incompatibilities for Tomcat users (beyond any > > issues that might affect Tomcat itself). Based on that, I've > > certainly been one of those casting aspersions. If we're all full of > > it, a [collections] statement on the nature and scope of backwards > > compatibility, pointing out the error of our (Tomcat developers and > > my) ways, would go a long ways towards addressing this concern. > > > > Struts is shortly going to be in the same boat ... the dependency of > > Struts itself on collections is only that inherited from > > Digester/BeanUtils; but the Struts developers will want to ensure that > > > an upgrade to Collections 3.0 won't cause undue problems for users of > > Struts, before we switch. > > i've been wondering if a possible solution might be to include > org.apache.commons.collections.ArrayStack and > org.apache.commons.collections.Buffer in with a new beanutils release. > these are very stable classes and only the javadocs have changed since > the 2.1 collections release. I don't have beanutils source in front of me but why do we even need ArrayStack at all? It doesn't seem to do anything that standard Java collection classes don't already provide. I'm assuming Buffer is only needed because ArrayStack implements it? It would be nice to make a clean break from Commons Collections and not include duplicate classes from its jar. David > > i think that this would buy us a little time to fix the problem > properly (in beanutils2 and digester2). > > i'm little reluctant to put betwixt on hold right now (i'm very close > to being able to merge back in the refactoring branch) but i think i'll > try to concentrate my efforts on digester and beanutils since these > problems seem both important and quite pressing. > > - robert > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org > For additional commands, e-mail: commons-dev-help@jakarta.apache.org > __________________________________ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org