logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralph Goers (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LOG4J2-95) Adding a custom appender Appender
Date Tue, 04 Dec 2012 01:13:58 GMT

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

Ralph Goers updated LOG4J2-95:
------------------------------

    Fix Version/s: 2.0-beta3
    
> 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
>             Fix For: 2.0-beta3
>
>         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


Mime
View raw message