avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephen McConnell <mcconn...@apache.org>
Subject Re: More "academic" ideas [Was: [VOTE] New sandbox project]
Date Thu, 11 Mar 2004 16:38:55 GMT
Farr, Aaron wrote:

>>-----Original Message-----
>>From: Hamilton Verissimo de Oliveira (Engenharia - SPO)
>>Sent: Thursday, March 11, 2004 9:04 AM
>>To: Avalon Developers List
>>Subject: Re: More "academic" ideas [Was: [VOTE] New sandbox project]
>>-----Mensagem original-----
>>De: Leo Sutic [mailto:leo.sutic@inspireinfrastructure.com]
>>>Since the Avalon 4 spec clearly states the order in which
>>>the lifecycle stages are performed, it makes no sense to
>>>allow the user to change the order for an A4 component.
>>>I'm a fan of:
>>> + order of additions of aspects doesn't matter
>>> + all aspects are optional and independent
>>> + it is hard to get a damaged configuration
>>> + it is obvious what effects an addition has
>>Sure. But this is not another "one man show" so we have to reach a common
> The reason I thought about "order matters" was to make it easier to custom
> lifecyles to be added (ie- lifecycle extensions).  Currently lifecycle or
> stage extensions usually end up being run after something like
> "initialize()" but that was never clarified in the exalibur-lifecycle
> package.

I'm sure this is documented - extensions are executed immediately prior 
to the initialization of the component (create stage) and immediately 
prior to the disposal of the component (destroy stage).  The order of 
execution of a an extension stage is based on the order in which the 
stage dependeny is declared.



| Magic by Merlin                                |
| Production by Avalon                           |
|                                                |
| http://avalon.apache.org/merlin                |
| http://dpml.net/merlin/distributions/latest    |

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

View raw message