>Stephen McConnell wrote:
>
> Does you component directive assert activation on startup - e.g.:
>
>   <component name="fred" class="WhateverImpl" activation="startup"/>

It didn't. When adding this, it works! But strange that I had to add this
now. Before, it worked without any explicit activation. Has the default
behaviour changed?

> Just a note concerning activation - the default behaviour is then any 
> component declared using <component> will have activation on startup 
> enabeld by default - unless the component type is transient.  

Sounds like the default changes for all components in the system... This is
certainly true for WhateverImpl when using the activation attribute. What
about other components not using the activation attribute? Does the default
change for any component declaration within the same block.xml
(<container>), or even for any component running in the system? I would
expect that each component has its default which may be overridden by the
activation attribute for the component meant by the name attribute, so in:

<container>
    <component name="fred" class="WhateverImpl" activation="startup"/>
    <component name="alf" class="WhatelseImpl"/>
</container>

That fred is activated on startup and alf is default.

> So for 
> example, if WhateverImpl class contains a component tag looks like:
>
>   @avalon.component name="xyz"
>
> then the component will default to a "transient" lifestyle in which case 
> activation on startup will be false - however, this can be overriden by 
> declaring the activation="startup" policy in the component directive.

So transient is default, which may be overridden in the component
configuration within block.xml -- for that component (and no others). I
suppose the lifestyle attribute of the avalon.component javadoc tag has
nothing to do with the activation?

> You updated the version of merlin-unit to 3.3-SNAPSHOT?

I did. 

I just started thinking we will never sort these issues out. Now I can start
developing... hopefully. Or at least start running into the next issues.

Thanks,
Daniel


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to