Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 68777 invoked from network); 11 May 2002 00:10:01 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 11 May 2002 00:10:01 -0000 Received: (qmail 13214 invoked by uid 97); 11 May 2002 00:10:02 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 13198 invoked by uid 97); 11 May 2002 00:10:01 -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 13186 invoked by uid 98); 11 May 2002 00:10:00 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) X-Authentication-Warning: costinm.sfo.covalent.net: costinm owned process doing -bs Date: Fri, 10 May 2002 17:08:03 -0700 (PDT) From: X-X-Sender: To: Tomcat Developers List Subject: Re: [4.1] Add additional events In-Reply-To: <20020510165115.F56198-100000@icarus.apache.org> Message-ID: 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: daedalus.apache.org 1.6.2 0/1000/N > > I plan to add additional events to the components start and stop methods: > > before_start, after_start, before_stop, after_stop. This has been suggested > > and discussed a while ago, but never actually implemented. Could you also add events for webapp add/remove/start/stop, and make sure the events are propagated up to coyote ? Costin -- To unsubscribe, e-mail: For additional commands, e-mail: