Return-Path: 
 <commons-dev-return-69468-apmail-jakarta-commons-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org
Received: (qmail 4414 invoked from network); 23 Mar 2005 18:41:25 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 23 Mar 2005 18:41:25 -0000
Received: (qmail 33197 invoked by uid 500); 23 Mar 2005 18:41:22 -0000
Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org
Received: (qmail 33118 invoked by uid 500); 23 Mar 2005 18:41:21 -0000
Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:commons-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:commons-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:commons-dev-help@jakarta.apache.org>
List-Post: <mailto:commons-dev@jakarta.apache.org>
List-Id: "Jakarta Commons Developers List" <commons-dev.jakarta.apache.org>
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Delivered-To: mailing list commons-dev@jakarta.apache.org
Received: (qmail 33104 invoked by uid 99); 23 Mar 2005 18:41:21 -0000
X-ASF-Spam-Status: No, hits=2.5 required=10.0
	tests=DNS_FROM_RFC_ABUSE,FORGED_YAHOO_RCVD
X-Spam-Check-By: apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Received: from web31711.mail.mud.yahoo.com (HELO web31711.mail.mud.yahoo.com)
 (68.142.201.191)
  by apache.org (qpsmtpd/0.28) with SMTP; Wed, 23 Mar 2005 10:41:20 -0800
Received: (qmail 49472 invoked by uid 60001); 23 Mar 2005 16:54:36 -0000
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  b=3/x8WZDK+bTt135TQExtfu4x49If41idL3VZBmhieOiB2VzWYfRL0zt1cBpLR8KYLFEcyr5NrvjNFD2D6G0zVBvbgx/aHx5bp3451rg0PIm2Aa/4zrjMGM5prkbhEBgyk6sjNF/Tx8j31ZQFZ5geV4YnFvh6Lo5n+HE5AzBQ4DM=
  ;
Message-ID: <20050323165436.49470.qmail@web31711.mail.mud.yahoo.com>
Received: from [67.104.107.34] by web31711.mail.mud.yahoo.com via HTTP;
 Wed, 23 Mar 2005 08:54:36 PST
Date: Wed, 23 Mar 2005 08:54:36 -0800 (PST)
From: Brian Stansberry <bes_commons_dev@yahoo.com>
Subject: Re: [logging, beanutils,
 others] Initial proposal for java.lang.ContextClassLoaderLocal or
 java.lang.Singleton
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>,
  Phil Steitz <phil.steitz@gmail.com>
In-Reply-To: <8a81b4af05032219516d8c9428@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Virus-Checked: Checked
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N


--- Phil Steitz <phil.steitz@gmail.com> wrote:

> Thanks, Simon.  Much clearer now.   
> 
> <snip/> 
> 
> > No, I mean the situation where a container
> continues running, while a webapp
> > or EJB running within it is stopped & restarted
> (potentially with updated
> > code).
> 
> OK,  so then lifecycle events should get triggered.

In the case of EJBs, are there any deployment-scope
lifecycle callbacks analogous to the Servlet API's
ServletContextListener?  All the callbacks I'm aware
of are scoped to individual beans within the pool, not
to the pool itself or to the overall EJB jar
deployment.

If, for example, a stateless session bean used the
commons-foobar library which in turn used JCL for
logging, we wouldn't want the JCL cleanup code to be
called each time ejbRemove() was invoked. 
Particularly not if the SLSB was just one of many
different beans deployed together, all of which
somehow use JCL.

Brian


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - now with 250MB free storage. Learn more. 
http://info.mail.yahoo.com/mail_250

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org