[jboss-jira] [JBoss JIRA] (LOGMGR-180) Create new LogContextSelector which selects the first caller that is not a log API

[James Perkins (JIRA)]

     [ https://issues.jboss.org/browse/LOGMGR-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Perkins updated LOGMGR-180:
---------------------------------
    Fix Version/s: 1.5.9.Final
                   2.0.8.Final
                   2.1.0.Alpha6


> Create new LogContextSelector which selects the first caller that is not a log API
> ----------------------------------------------------------------------------------
>
>                 Key: LOGMGR-180
>                 URL: https://issues.jboss.org/browse/LOGMGR-180
>             Project: JBoss Log Manager
>          Issue Type: Enhancement
>            Reporter: James Perkins
>            Assignee: James Perkins
>             Fix For: 1.5.9.Final, 2.0.8.Final, 2.1.0.Alpha6
>
>
> There is a need in WildFly for a log context selector that short-circuits after the first callers class loader that is not a log API. All log API's would have to be registered. The call stack would be walked and once a class loader is found that is not registered as a log API class loader, that caller would be used to determine whether or not a registered log context should be used. If no context is associated with the caller, the default log context will be used and the call stack walking will stop.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)