Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <3F995A94.2020208@apache.org>
Date: Fri, 24 Oct 2003 13:00:04 -0400
From: Berin Loritsch <bloritsch@apache.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.4) Gecko/20030624
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Mass update to components for Cocoon 2.2
References: <84F0A43A4248CE45B5C0E20F4C40779C667C4D@naomi.webworks.nl>
 <3F970ABA.9000601@leverageweb.com> <3F995286.1030603@apache.org>
 <3F995528.8020104@apache.org> <3F995810.1060001@leverageweb.com>
In-Reply-To: <3F995810.1060001@leverageweb.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Geoff Howard wrote:
> Berin Loritsch wrote:
> 

> 
> Ok, speaking of dependencies...
> 
> We have some components which can accept the name of a component to 
> lookup  and use.  For instance in the config, a Role or shorthand is 
> provided and the component looks that up directly.  How does that fit in 
> with the explicit declaration of dependencies?  I'll have to dig up an 
> example later if I haven't made it clear enough yet.

Just the interface used is enough for Fortress.  The thing is we want to
ensure that components are brought up and shut down in the proper order.
So, if one class uses a Generator, then we only need to declare "Generator",
not any particular hint name.

Even if for some reason we have a "Generator" mapped directly to "foo" with
no role hint info, we need "Generator" declared because that is what the
dependency is.

Now that I looked at the implementation, and the dependency info is not
inherited at this time.  That is a future thing on the books.

-- 

"They that give up essential liberty to obtain a little temporary safety
  deserve neither liberty nor safety."
                 - Benjamin Franklin