cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carsten Ziegeler <>
Subject Re: Logkit (I know, again) was [RT] Using Spring instead of ECM++
Date Sun, 19 Feb 2006 18:08:59 GMT
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?

> Anyway here's my +1 for it.
Carsten Ziegeler - Open Source Group, S&N AG

View raw message