Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 89598 invoked from network); 3 Jan 2002 01:58:55 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 3 Jan 2002 01:58:55 -0000 Received: (qmail 15847 invoked by uid 97); 3 Jan 2002 01:58:56 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 15831 invoked by uid 97); 3 Jan 2002 01:58:55 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 15773 invoked from network); 3 Jan 2002 01:58:55 -0000 Date: Wed, 2 Jan 2002 17:58:45 -0800 (PST) From: "Craig R. McClanahan" To: Tomcat Developers List Subject: Re: [PATCH][4.0] ApplicationFilterChain Ctr In-Reply-To: <3C30DFD7.110423D2@distributopia.com> Message-ID: <20020102175556.R31528-100000@icarus.apache.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: localhost 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Mon, 31 Dec 2001, Christopher K. St. John wrote: > Date: Mon, 31 Dec 2001 15:59:51 -0600 > From: Christopher K. St. John > Reply-To: Tomcat Developers List > To: tomcat-dev@jakarta.apache.org > Subject: [PATCH][4.0] ApplicationFilterChain Ctr > > > ApplicationFilterChain has a constructor that doesn't do > anything useful. It's call to super() is a bit confusing, > since it leads to the assumption that FilterChain is a > class. Other interface implementations in Catalina don't > bother with placeholder constructors, this patch removes > the one in ApplicationFilterChain. > Christopher, I'm going to look at your suggestions for ApplicationFilterChain and StandardPipeline, but would like to wait a few days before committing anything -- I'm almost at a code freeze on an (internal) project using Tomcat, and would like to not do anything stupid at this point. I've committed the typo-fixes (and I agree with you that they make life better). > I've been posting patches as I come across bits of code > and documentation that look iffy. None of them have been > showstoppers and none of them are the kind of thing normal > people can work up much enthusiam about. But crappy little > cleanup patches really do help in the long run. Especially > documentation cleanup. I was under the impression that > stuff like this didn't go through the normal code-change > voting process, it just got picked up (or not) by a > committer and merged in. Is that correct? Would it be more > appropriate to submit bug reports? > You're correct about the process. I guess that I'd prefer to see stuff like this sent through the bug tracking system (http://nagoya.apache.org/bugzilla) just to make sure it doesn't get lost in the volume of messages on the mailing list. You can add the patch file as an attachment. But I'll still try to pay attention to them either way ... :-) > > -- > Christopher St. John cks@distributopia.com > DistribuTopia http://www.distributopia.com > Craig -- To unsubscribe, e-mail: For additional commands, e-mail: