Creator was set to act *just before* Initializable.initialize(). At least this is what I spoke of every time. The only other implementation of lifecycle extensions was Merlin. Is there any compelling reason why it wasn't the same?
The reason that Creator happens just before initialize() is because initialize is (other than start()) the last event that the component receives. Also, the initialize() method is the perfect place to deal with anything passed in while the component is being initialized. On the same token, the Destructor (or whatever it is called) should be called between Startable.stop() and Disposable.dispose(). > -----Original Message----- > From: Peter Donald [mailto:peter@;apache.org] > Sent: Saturday, November 09, 2002 3:27 AM > To: [EMAIL PROTECTED] > Subject: Creator Lifecycle extension > > > 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 :) > > So is there any overiding reason why creation is handled > differently from all > the other extensions or is it just happenstance? Can I fix it > and place the > creation intersection point at the end of the startup phase? > > -- > Cheers, > > Peter Donald > ----------------------------------------------------- > When a stupid man is doing something he's ashamed of, > he always declares that it is his duty. > George Bernard Shaw > ----------------------------------------------------- > > > -- > To unsubscribe, e-mail: > <mailto:avalon-dev-> [EMAIL PROTECTED]> > For > additional commands, > e-mail: <mailto:avalon-dev-help@;jakarta.apache.org> > -- To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>
