Return-Path: Delivered-To: apmail-jakarta-avalon-phoenix-dev-archive@apache.org Received: (qmail 68590 invoked from network); 18 Jul 2002 10:46:20 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 18 Jul 2002 10:46:20 -0000 Received: (qmail 167 invoked by uid 97); 18 Jul 2002 10:46:33 -0000 Delivered-To: qmlist-jakarta-archive-avalon-phoenix-dev@jakarta.apache.org Received: (qmail 115 invoked by uid 97); 18 Jul 2002 10:46:32 -0000 Mailing-List: contact avalon-phoenix-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon-Phoenix Developers List" Reply-To: "Avalon-Phoenix Developers List" Delivered-To: mailing list avalon-phoenix-dev@jakarta.apache.org Received: (qmail 84 invoked by uid 98); 18 Jul 2002 10:46:31 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Content-Type: text/plain; charset="iso-8859-1" From: Peter Royal To: "Avalon-Phoenix Developers List" Subject: Re: Architectural Question Date: Thu, 18 Jul 2002 06:39:54 -0400 User-Agent: KMail/1.4.1 References: <3D365E7F.7080400@prismtechnologies.com> In-Reply-To: <3D365E7F.7080400@prismtechnologies.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200207180639.54573.proyal@apache.org> 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 Thursday 18 July 2002 02:21 am, Steve Osselton wrote: > We're starting to use Avalon and have components that require persistent > initialization (creation of table/entries) and destruction (removal of said > tables/entries). I was wondering why this is not supported as a framework > activity interface? I was expecting so see something like a 'Persistent' > interface with 'create' and 'destroy' operations. Unfortunately I haven't been around long enough to give a good answer on why there is nothing akin to 'Persistent', other than it was never needed by everyone and thus never included in the core framework. With that said, I would recommend using Initializable and Disposable to handle your persistent needs. Also, what container are you using? Fortress now has support for an extensible lifecycle, http://jakarta.apache.org/avalon/excalibur/fortress/features.html and http://cvs.apache.org/viewcvs.cgi/jakarta-avalon-excalibur/fortress/src/xdocs/lifecycle-extensions.xml?rev=1.2&content-type=text/vnd.viewcvs-markup (I don't think its made it to the site yet). -pete -- peter royal -> proyal@apache.org -- To unsubscribe, e-mail: For additional commands, e-mail: