Return-Path: Delivered-To: apmail-jakarta-avalon-phoenix-dev-archive@apache.org Received: (qmail 2086 invoked from network); 18 Jul 2002 16:58:55 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 18 Jul 2002 16:58:55 -0000 Received: (qmail 25054 invoked by uid 97); 18 Jul 2002 16:59:12 -0000 Delivered-To: qmlist-jakarta-archive-avalon-phoenix-dev@jakarta.apache.org Received: (qmail 25018 invoked by uid 97); 18 Jul 2002 16:59:11 -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 25006 invoked by uid 98); 18 Jul 2002 16:59:10 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <3D36F39A.8060607@prismtechnologies.com> Date: Thu, 18 Jul 2002 17:58:02 +0100 From: Steve Osselton Organization: PrismTech User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020606 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Avalon-Phoenix Developers List Subject: Re: Architectural Question References: <3D365E7F.7080400@prismtechnologies.com> <200207180639.54573.proyal@apache.org> 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: daedalus.apache.org 1.6.2 0/1000/N Hi Peter, I agree that Initializable are Disposable are currently the places where this functionality can be bolted in. However I think that conceptually these are different to persistent creation/destruction. I was reading the developers guide which seemed very big on the separation of concerns which is why I though a new activity interface might be appropriate. Currently we are moving to use the framework classes with our own CORBA container. We are doing this as we are in effect migrating an existing system which we will probably complete in a number of stages. I'll have a look at Fortress to see what it offers. Cheers Steve. Peter Royal wrote: > 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 > -- To unsubscribe, e-mail: For additional commands, e-mail: