Peter Donald wrote:
Hi,
Currently the Creator extension gets run halfway through the startup phase.
Where most of the other lifecycle extensions occur at the start or end of the
phases. Personally I think that is the way it should be but Fortress
disagrees :)
The create extension interception point occurs as the last action pror
to initialization of the component. This is consitent across all
containers implementing the extension framework.
So is there any overiding reason why creation is handled differently from all
the other extensions or is it just happenstance?
Yes - there is an overriding reason - basically a creation time
extension falls into the same family of component/container interactions
that we see with enableLogging, contextaulization, configuration,
parmeterization, servicing. The all concern the establishment of the
appropriate component state *prior* to the initialization of the
component. A component implementation can then handle its own internal
verification of state during the initilization stage.
Can I fix it and place the
creation intersection point at the end of the startup phase?
You could, but you would breaking the implementation ;-)
Cheers, Steve.
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:mcconnell@;osm.net
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>
