avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicola Ken Barozzi <nicola...@apache.org>
Subject Re: [proposal] avalon 5 ComponentManager interface
Date Mon, 17 Jun 2002 13:34:59 GMT

Peter Donald wrote:
> At 01:38 PM 6/17/2002 +0200, you wrote:
>> As I described in my previous mails, I think that we need at least two 
>> levels of roles.
>>
>> -Roles
>> -Sub-Roles
> 
> 
> Each dependency must support multiple constraints (I would say that 
> there is a need to support N dimensions rather than just one). It does 
> not mean that each constraint must be passed into lookup() method.

Ok.
Wait... N dimensions? SF?


> the interface class is one constraint.
> the subtype (like html vs xml vs svg serializers) is anothe constraint.

Correct.

>> Cocoon uses the *same* interfact to handle them (role) but they have a 
>> very different behaviour (subrole).
>>
>> If I remove the role-subrole thing, how can Cocoon discern how to 
>> handle the component (Serializer, Transformer, etc...)? Do I have to 
>> declare them all separately, and not as a group?
> 
> 
> Leos described it already. You declare dependencys of each component in 
> metadata. You then have providers mapped into consumers in sitemap (or 
> whatever assembly file you want to use).

Ok, this makes sense, but I still think that there are two different 
role levels, the "what" and the "how".

This is about semantics; you are still thinking about only one level of 
dependency.

-- 
Nicola Ken Barozzi                   nicolaken@apache.org
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------


--
To unsubscribe, e-mail:   <mailto:avalon-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@jakarta.apache.org>


Mime
View raw message