Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 73665 invoked from network); 14 Mar 2002 04:13:56 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 14 Mar 2002 04:13:56 -0000 Received: (qmail 3228 invoked by uid 97); 14 Mar 2002 04:14:04 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@jakarta.apache.org Received: (qmail 3212 invoked by uid 97); 14 Mar 2002 04:14:03 -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 3201 invoked from network); 14 Mar 2002 04:14:03 -0000 Date: Thu, 14 Mar 2002 13:05:45 +0900 From: Ryan Shaw To: "Avalon Developers List" Subject: Re: Using cornerstone blocks without phoenix? Message-Id: <20020314130545.609fbc1a.ryan@silveregg.co.jp> In-Reply-To: <005001c1ca63$074e9c90$0a01a8c0@osm.net> References: <3C8F012F.80404@yahoo.com> <005001c1ca63$074e9c90$0a01a8c0@osm.net> Organization: Silver Egg Technology Co., Ltd. X-Mailer: Sylpheed version 0.7.2claws2 (GTK+ 1.2.10; i386-debian-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII 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 Very cool! Thanks for the detailed instructions. I'm amazed it is as easy as that...are you sure this is an Open Source project? You're supposed to just say, "Read the source!" :^) Ryan Stephen wrote: ||| ||| Yep, it's totally feasible all you need is a little magic ||| from Merlin :-) ||| ||| 1. Checkout org.apache.avalon-apps/enterprise/tools ||| 2. $ cd /enterprise/tools ||| 2. $ ant dist ||| 3. $ ant export ||| 4. and the following to your project's build file ||| ||| ||| ||| ||| ||| ||| ||| ||| ||| ||| - target is any class that has a corresponding .xinfo file. ||| - priority value is either INFO, ERROR, WARNING, DEBUG ... i.e. ||| logging level. ||| - disposal id TRUE simply terminates the run, or FALSE lets it ||| live on as a server ||| - verbose if TRUE provides debug level info about what the container ||| is doing with your components ||| - configuration is an optional attribute you can provide that references ||| a configuration file or you can include a default ||| statement in your .xinfo file (see package demo for example) ||| - you can have multiple fileset declarations - this basically ||| populates the classloader and sets up a registry of available ||| services if the target component needs them based on supplied ||| jar files containing block manifest entries ||| - check package documentation for lots of additional details ||| ||| Note - the "$ ant export" statement above will put a copy of ||| avalon-frameork.jar, logkit.jar and merlin.jar into your Ant lib ||| directory. After that your ready to roll. ||| ||| Cheers, Steve. ||| ||| ||| > -----Original Message----- ||| > From: Paul Hammant [mailto:Paul_Hammant@yahoo.com] ||| > Sent: Wednesday, 13 March, 2002 08:35 ||| > To: Avalon Developers List ||| > Subject: Re: Using cornerstone blocks without phoenix? ||| > ||| > ||| > Ryan, ||| > ||| > >How feasible is it to use cornerstone services/blocks without phoenix? ||| > > ||| > Blocks? Yes it shold be doable. All you have to do is instantiate a ||| > block and decorate it with it's IoC requirements in the same way that ||| > Phoenix does. What you might end up with would be a microPhoenix. Hmm ||| > that rings a bell. ||| > ||| > - Paul ||| > ||| > ||| > -- ||| > 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: