Bernd Fondermann wrote:
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.
... and the correct behavior committed to the Spring sandbox.
Thanks again, Stefano, for pointing out what really went wrong!
Booting the server is getting really far now. In fact, the server comes
up (with some tweaking).
That's been a big step forward.
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
