Return-Path: Delivered-To: apmail-incubator-directory-dev-archive@www.apache.org Received: (qmail 23350 invoked from network); 4 Dec 2003 21:15:45 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 4 Dec 2003 21:15:45 -0000 Received: (qmail 72653 invoked by uid 500); 4 Dec 2003 21:15:34 -0000 Delivered-To: apmail-incubator-directory-dev-archive@incubator.apache.org Received: (qmail 72608 invoked by uid 500); 4 Dec 2003 21:15:33 -0000 Mailing-List: contact directory-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Apache Directory Developers List" Reply-To: "Apache Directory Developers List" Delivered-To: mailing list directory-dev@incubator.apache.org Received: (qmail 72584 invoked from network); 4 Dec 2003 21:15:33 -0000 Received: from unknown (HELO osm.net) (212.198.17.4) by daedalus.apache.org with SMTP; 4 Dec 2003 21:15:33 -0000 Received: from localhost ([127.0.0.1]) by osm.net (JAMES SMTP Server 3.0a1) with SMTP ID 970 for ; Thu, 4 Dec 2003 22:18:11 +0100 (CET) Message-ID: <3FCFA48E.602@apache.org> Date: Thu, 04 Dec 2003 22:18:06 +0100 From: Stephen McConnell User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en, en-us MIME-Version: 1.0 To: Apache Directory Developers List Subject: Re: [eve] Event Manager References: <20031204193434.OWPE1936.imf25aec.mail.bellsouth.net@franklin> <200312041456.40159.wmckean@logictrends.com> <200312041531.05283.wmckean@logictrends.com> In-Reply-To: <200312041531.05283.wmckean@logictrends.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Wes McKean wrote: >I really like the Event Notifier Pattern. May I take a stab at this? If so, >should I write it for Merlin? Or should I create something generic that can >be imbedded in any container? The container could then implement a standard >interface or something. > What Avalon has been working towards is the general minimization of the concern that a component has with respect to the container that it is running within. You will need to follow some rules - for example if you need access to resources (such as a working directory) then you need to use establish Avalon resource names and the @avalon javadoc tags. Providing you stick with the avalon contract you should not have any trouble running your component in other containers because they all claim to support Avalon. If you need any help on the Merlin container just yell out and I can give you a hand - or if you want just post a message over on dev@avalon where a couple of hundred people are lurking around and amongst them is a lot of Merlin experience. Cheers, Stephen. -- Stephen J. McConnell mailto:mcconnell@apache.org |------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/ | |------------------------------------------------|