Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org Received: (qmail 99231 invoked from network); 13 Nov 2003 13:01:05 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 13 Nov 2003 13:01:05 -0000 Received: (qmail 82768 invoked by uid 500); 13 Nov 2003 13:00:38 -0000 Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 82662 invoked by uid 500); 13 Nov 2003 13:00:37 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 82649 invoked from network); 13 Nov 2003 13:00:37 -0000 Received: from unknown (HELO sid.armstrong.com) (204.74.20.252) by daedalus.apache.org with SMTP; 13 Nov 2003 13:00:37 -0000 Received: from joedog.org (fnord.armstrong.com [204.74.20.14]) by sid.armstrong.com (8.12.8p1/8.12.8) with ESMTP id hADCo0C0002457 for ; Thu, 13 Nov 2003 07:50:00 -0500 Message-ID: <3FB38071.5050008@joedog.org> Date: Thu, 13 Nov 2003 08:00:33 -0500 From: Tim Funk Organization: Human being User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en, es-mx, de, sv MIME-Version: 1.0 To: Tomcat Users List Subject: Re: SessionListener References: <3FB32513.7080601@noterik.nl> <3FB37F53.904@comcast.net> <3FB37E9A.10605@noterik.nl> In-Reply-To: <3FB37E9A.10605@noterik.nl> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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 You might be able to use HttpSessionAttributeListener -Tim Peter Maas wrote: > What I actually want to do is call some destruct methods in objects > bound to the session... > > P > > Christopher Schultz wrote: > >> Peter, >> >>> I wondered if there is a way detect somehting like a >>> 'sessionWillBeDestroyed' event. >>> since the sessionDestroyed method in a sessionListener seems to be >>> called after the session was destroyed. >> >> >> >> I don't think you can 'veto' the destruction of a session, if that's >> what you mean. All the container will do is notify you that the >> session is in the process of being destroyed. >> >> -chris >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org >> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org >> >> >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org