Giacomo Pati schrieb: >>> Now, with Spring I would suggest the following approach: >>> Cocoon uses an own application context which can be compared (by >>> simplifying) with a service manager. So we have an application context >>> for the core of Cocoon (again simplified). Now you can define a root >>> Spring application context using the usual Spring context listener and >>> this one (if present) will be the parent context of our Cocoon core context. >>> If you define your own logger bean in this spring application context, >>> Cocoon will use that logger instead. If the spring app context is >>> missing or does not define a logger bean we will define a log4j logger >>> in the core application context. So it would be possible to use your own >>> logging abstraction while Cocoon does nearly nothing to support it. > > This is meant for traditional Avalon Components implementing LogEnabled, > right? > Yes.
> Anyway here's my +1 for it. > Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
