You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@geronimo.apache.org by "Ivan (JIRA)" <ji...@apache.org> on 2009/04/08 12:14:13 UTC

[jira] Updated: (GERONIMO-4615) Make the client application could use their own Log4j configuration with ApplicationLog4jConfigurationGBean

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

Ivan updated GERONIMO-4615:
---------------------------

          Component/s: Logging
    Affects Version/s: 2.2
                       2.1.5

> Make the client application could use their own Log4j configuration with ApplicationLog4jConfigurationGBean
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-4615
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4615
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: Logging
>    Affects Versions: 2.1.5, 2.2
>            Reporter: Ivan
>            Assignee: Ivan
>            Priority: Minor
>
> Currently, while using the ApplicationLog4jConfigurationGBean to do log4j configuration, we share the same Log4j configuration, it may caused some conflict.
> Such as the configurations for the same packages in the different applications will be overwritten.

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