[prev in list] [next in list] [prev in thread] [next in thread] 

List:       log4j-dev
Subject:    [jira] [Comment Edited] (LOG4J2-95) Adding a custom appender Appender
From:       "Ralph Goers (JIRA)" <jira () apache ! org>
Date:       2012-10-24 19:30:12
Message-ID: 812914318.23757.1351107012695.JavaMail.jiratomcat () arcas
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/LOG4J2-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13483499#comment-13483499 \
] 

Ralph Goers edited comment on LOG4J2-95 at 10/24/12 7:28 PM:
-------------------------------------------------------------

I'll have to download RFT but if I understand correctly the class path organization \
has the Log4j classes in a parent class loader and the log4j plugin classes in a \
child class loader.  If I were to extrapolate this to an environment such as Tomcat \
this would be like having the Log4j files in Tomcat's lib directory and the log4j \
plugins in the web app. Hopefully you would understand why it could be a bad idea for \
Log4j to be loading classes from a child class loader if the configuration is also at \
the Tomcat level. However, if the configuration is in the Web app it would make sense \
for the plugins to be located. 

So even without getting RFT you may have given me a few ways to try to emulate this.
                
      was (Author: ralph.goers@dslextreme.com):
    I'll have to download RFT but if I understand correctly the class path \
organization has the Log4j classes in a parent class loader and the log4j plugin \
classes in a child class loader.  If I were to extrapolate this to an environment \
such as Tomcat this would be like having the Log4j files in Tomcat's lib directory \
and the log4j plugins in the web app. Hopefully you would understand why it would be \
a bad idea for Log4j to be loading classes from a child class loader in that case.  
> Adding a custom appender Appender
> ---------------------------------
> 
> Key: LOG4J2-95
> URL: https://issues.apache.org/jira/browse/LOG4J2-95
> Project: Log4j 2
> Issue Type: Question
> Components: Configurators
> Affects Versions: 2.0-beta1
> Environment: Windows 7 x64, Java 7 x86, Eclipse 3.8.1 x86, Eclipse RCP plugin \
>                 application
> Reporter: Robert Breunung
> Labels: appender, extend
> Attachments: Desktop.png, happyTestProject.rftjdtr, LogDemo.zip
> 
> 
> Hello,
> since two days I'm working with Log4j 2 . I try to migrate from Log4J. I'm using it \
> in an Eclipse application. I put the necessary jars of the binary distribution into \
> a basic plugin and a log4j2.xml into the root. This worked well so far. Now I tried \
> to add a custom appender to log4j. The class is in the default source package of \
> the Eclipse plugin. Annotations are set like in the homepage documentation. In the \
> first try I tried to provide the package of the Appender via the log4j2.xml. I set \
> the attribute package in the configuration element. It seemed to me, the attribute \
> is completely ignored? At least the class from the given package was not loaded. In \
> the second try I tried to provide the package via the static method \
> '...log4j.core.config.plugin.PluginManager.addPackage'. I debugged the method to \
> get a hint why it didn't work. It tried to transform my package \
> 'com.application.logging' into a URI 'com/application/logging' and started to \
> search with it somehow. It might have found them treating them as file, as the \
> classes were lying in a subdirectory. But as there was no file scheme in the \
> beginning of the URI, it searched a not existing jar. The XML parser of the \
> configuration can't resolve the name of my appender in the end. Do you have an idea \
> then I do anything wrong, or then there is an open issue? I can provide more \
> details on request. Is there a programmatical way to register my appender to Log4J \
> 2 before the Logger initialization? Sincerely
> Robert Breunung

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]