Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 71236 invoked from network); 13 Apr 2002 14:01:56 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 13 Apr 2002 14:01:56 -0000 Received: (qmail 26949 invoked by uid 97); 13 Apr 2002 14:01:58 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@jakarta.apache.org Received: (qmail 26933 invoked by uid 97); 13 Apr 2002 14:01:57 -0000 Mailing-List: contact avalon-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon Developers List" Reply-To: "Avalon Developers List" Delivered-To: mailing list avalon-dev@jakarta.apache.org Received: (qmail 26918 invoked from network); 13 Apr 2002 14:01:57 -0000 Message-ID: <3CB8374B.7090904@yahoo.com> Date: Sat, 13 Apr 2002 14:48:59 +0100 From: Paul Hammant User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.9) Gecko/20020311 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Avalon Developers List Subject: Re: Lifecycleable interface References: <20020410125948.34609.qmail@web13403.mail.yahoo.com> 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 James, I think that in the end, the guys have a point in that this does not fit Phoenix very well. It does sorta break the IoC idea. A redeeming pont is that the way Jeskop mounts apps that are largely already writen there is a lot of breaking of IoC going on inside the scope of that hosted app. As such, and becase of the hot-pluggable nature, I am going to create the interface after all, but inside Jesktop. - Paul >Paul, > >As an application developer, I am fully appreciate what you are going to do. > >Phoenix has a drawback as a server/container of other application >containers(i.e. serlvet, EJB, Jesktop etc..). It doesn't provide a simple, >united way to allow applications(i.e., a servlet deployed in a serlvet >engine contained in phoenix) to communicate with the phoenix kernel, other >sars, and other blocks assemble within the same sar. > >I hope in the future, I can answer the question 'Why deploy a servlet in Jo! >running inside Phoenix, but not a standalone Jo! environment' as 'The >servlet can utilize services provided by other phoenix blocks'(The Beauty of >Phoenix). > >James Lau > >----- Original Message ----- >From: "Paul Hammant" >To: "Avalon" >Sent: Wednesday, April 10, 2002 8:59 PM >Subject: Lifecycleable interface > > >>I am about to do some more work on Jesktop (given there is more >> >competition currently). Nicola > >>Ken suggested that Jesktop could benefit from general services and I am >> >inclided to do that, but > >>maybe there is a case for a hot-puggable system like Jesktop to have a >> >Lifecycleable api. As this > >>possibly applies to Avalon in genral. As such, I'd like to propose it here >> >: > >>interface Lifecycleable { >> // int getStage(); // maybe ? >> String getLifecycleInterface(); >> void startupLifecycle(Object obj); >> void shutdownLifecycle(Object obj); >>} >> >>DefaultLogEnabledLifecyclable extends AbstractLogEnabled implemnents >> >Lifecyclable{ > >> public String getLifecycleInterface() { >> retrurn "org.apache.avalon.framework.LogEnabled"; >> } >> public void startupLifecycle(Object obj) { >> ((LogEnabled) obj).enableLogging(getLogger()); >> } >> public void shutdownLifecycle(Object obj) { >> ((LogEnabled) obj).enableLogging(null); //maybe >> } >>} >> >>And similar for Iniializable, Startable, Dooable, Blahable... >> >>Thoughts? >> >>- Paul >> >>__________________________________________________ >>Do You Yahoo!? >>Everything you'll ever need on one web page >>from News and Sport to Email and Music Charts >>http://uk.my.yahoo.com >> >>-- >>To unsubscribe, e-mail: >> > > >>For additional commands, e-mail: >> > > >> > >-- >To unsubscribe, e-mail: >For additional commands, e-mail: > > > -- To unsubscribe, e-mail: For additional commands, e-mail: