Berin Loritsch wrote:
> Stephen McConnell wrote:
>
>>
>>
>> Berin Loritsch wrote:
>>
>>> The link on the web site:
>>>
>>> http://jakarta.apache.org/avalon/excalibur/container/attributes.html
>>>
>>> avalon:name java.lang.String The name of a component (is this
>>> really necessary?)
>>
>>
>>
>>
>> It not "necessary" but it is convinient for two reasons. Firstly it
>> provides a hook to the component instance name assigned by a
>> container when having to deal with things like BlockContext.
>> Secondly, it is useful in error message generation by a component
>> implementation.
>
>
> Just keep in mind that under your proposal, a Component can go by many
> names. I have to assume that you are refering to the assembly.xml
> declared name as opposed to the lookup role name.
>
Basically correct - however, a componay can be created in Merlin without
explicit declaration at the assmbly level. For example, a componet
profile can be declared in a package. The package supplied name may
conflict with a name already declared at assembly scope in which case
the container needs to provide a non-confliciting name for the component
instance it is introducing.
Cheers, Steve.
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:[EMAIL PROTECTED]
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
