geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (GERONIMO-4615) Make the client application could use their own Log4j configuration with ApplicationLog4jConfigurationGBean
Date Wed, 08 Apr 2009 14:13:13 GMT

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

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

    Attachment: Geronimo-4615.patch

After adding the configuration below to the deployment plan
---
<dep:dependency>
            <dep:groupId>log4j</dep:groupId>
            <dep:artifactId>log4j</dep:artifactId>
            <dep:type>jar</dep:type>
        </dep:dependency>
        
        </dep:dependencies>
        <dep:hidden-classes>
             <dep:filter>org.apache.log4j</dep:filter>             
        </dep:hidden-classes>
---
and applying the patch file, the user application will load and config log4j in its own classloader
scope. So that the conflict issue will disapper.
Could anyone help to review it, if no proble, I would like to commit those changes and update
the documents.
Thanks !

> 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
>         Attachments: Geronimo-4615.patch
>
>
> 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.


Mime
View raw message