logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Woonsan Ko (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LOG4J2-313) JNDI Lookup plugin support
Date Wed, 17 Jul 2013 20:55:46 GMT

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

Woonsan Ko updated LOG4J2-313:

    Attachment: jndi-lookup-plugin.patch
> JNDI Lookup plugin support
> --------------------------
>                 Key: LOG4J2-313
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-313
>             Project: Log4j 2
>          Issue Type: New Feature
>            Reporter: Woonsan Ko
>             Fix For: 2.0-beta9
>         Attachments: jndi-lookup-plugin.patch
> Currently, Lookup plugins [1] don't support JNDI resources.
> It would be really convenient to support JNDI resource lookup in the configuration.
> One use case with JNDI lookup plugin is as follows:
>   I'd like to use RoutingAppender [2] to put all the logs from the same web application
context in a log file  (a log file per web application context).
> And, I want to use JNDI resources look up to determine the target route (similarly to
JNDI context selector of logback [3]).
> Determining the target route by JNDI lookup can be advantageous because we don't have
to add any code to set properties for the thread context and JNDI lookup should always work
even in a separate thread without copying thread context variables.
> [1] http://logging.apache.org/log4j/2.x/manual/lookups.html
> [2] http://logging.apache.org/log4j/2.x/manual/appenders.html#RoutingAppender
> [3] http://logback.qos.ch/manual/contextSelector.html

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

View raw message