cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler (JIRA)" <j...@apache.org>
Subject [jira] Updated: (COCOON-2147) Log4j configuration is loaded too late with Spring Configurator
Date Thu, 15 Nov 2007 19:30:43 GMT

     [ https://issues.apache.org/jira/browse/COCOON-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Carsten Ziegeler updated COCOON-2147:
-------------------------------------

    Summary: Log4j configuration is loaded too late with Spring Configurator  (was: Log4j
configuration is loaded to late with Spring Configurator)

> Log4j configuration is loaded too late with Spring Configurator
> ---------------------------------------------------------------
>
>                 Key: COCOON-2147
>                 URL: https://issues.apache.org/jira/browse/COCOON-2147
>             Project: Cocoon
>          Issue Type: Bug
>          Components: * Cocoon Core
>    Affects Versions: 2.2-dev (Current SVN)
>            Reporter: Carsten Ziegeler
>
> The spring configurator provides a bean for configuring log4j through a spring bean.
This bean is initialized as soon as spring is finding the definition and starts up the container.
Obviously this is too late as all log messages happening before this init are send "somewhere
else".
> 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
> c) Remove the logging configuration at all and leave it up to the users to configure
everything properly (more or less Spring does the same)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message