cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carsten Ziegeler <cziege...@apache.org>
Subject Re: Logging, Re: [jira] Created: (COCOON-2147) Log4j configuration is loaded to late with Spring Configurator
Date Thu, 15 Nov 2007 17:02:00 GMT
Vadim Gritsenko wrote:
> Carsten Ziegeler (JIRA) wrote:
>> Log4j configuration is loaded to late with Spring Configurator
> ...
>> There might be different solutions for this:
>> a) Provide a configuration servlet/servlet listener (Spring provides
>> one as well, but that's only usuable inside an expanded war file)
>> b) Create an XML tag for spring configuration (like we do for the
>> settings). This will ensure that logging is setup before beans are setup
> 
> I'd prefer either a or b. b is even better since you don't have to touch
> web.xml.

Yes, but with b) still this can be too late as you don't catch logging
statements from Spring happening before our logging tag is read.
Personally I could live with that.

Thinking about this, I have the feeling that it's not Cocoon's task to
configure logging. It's not our concern, it should more be the concern
of Spring as the core framework underneath everything.
But the interesting part is that even Spring has only partial support
for that. And I'm wondering why noone has complained about this yet.

> 
> Speaking of logging, I think latest jetty maven plugin (or something
> else?) broke all the logging and now everything is dumped to the
> console, and log file is empty. It started doing this for me day or two
> ago.
Strange, I think this happened a year ago with another jetty release as
well. It was afaik some changes in class loading hierarchy and provided
jars from jetty.

Carsten

-- 
Carsten Ziegeler
cziegeler@apache.org

Mime
View raw message