Stefano, Thanks for your comment!
I just debugged James(Phoenix) and was very surprised to find that the lifecycle calling sequence is traversing deep (all lifecycle methods for one component, then for the second) instead of calling one lifecycle method for all components, then the next method for all components. I don't know how I got to assume it must be the other way round, but this way it makes even less sense to me to have that many lifecycle methods and interfaces! I have to go now to refactor James/Spring bootstrapping. I wonder how that ever worked out (as it appeared to) for releases 2.3.0 and .1! The AbstractJamesService refactoring proposal is retracted. Bernd On 7/29/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote: > Bernd Fondermann ha scritto: > IIRC this is the right order for initialization: > enableLogging > contextualize > service > parameterize > configure > initialize > start > > So inside call you should have already received fully initialized > dependencies. > > > configure() should only be used for reading configuration attributes, > > not for doing anything more or even calling sibbling components. > > Not sure this is a requirement of the avalon contract at all. Btw > configure and initialize are called one after the other, with no changes > to the dependencies in the mean time. Btw if moving code from configure > to intialize fix your issue, feel free to move that code. > The point in doing things in configure instead of initialize is to be > able to catch configurations errors before running through the > initialization, otherwise everything can be delayed to initialization. > > > I will try now to split configureHelloName() into configureHelloName() + > > initializeHelloName(). > > > > Does that sound reasonable? > > > > Bernd > > If this helps +1, but I think you should look for the problem in the > spring-avalon wrapper as from my understanding there is no avalon > contract that is fixed by the action you propose. > > Stefano > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
