[jboss-jira] [JBoss JIRA] (WFCORE-4807) Add option to route log messages based on the current thread's class loader

[James Perkins (Jira)]

     [ https://issues.redhat.com/browse/WFCORE-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Perkins moved EAP7-1421 to WFCORE-4807:
---------------------------------------------

                          Project: WildFly Core  (was: JBoss EAP Planning for version 7 and above)
                              Key: WFCORE-4807  (was: EAP7-1421)
                       Issue Type: Feature Request  (was: Requirement)
                         Workflow: GIT Pull Request workflow   (was: EAP Agile Workflow 2.0)
                      Component/s: Logging
                                       (was: Logging)
                   EAP Testing By:   (was: Engineering)
          EAP PT Pre-Checked (PC):   (was: TODO)
                   Target Release:   (was: 7.4.0.GA)
       EAP PT Community Docs (CD):   (was: TODO)
         EAP PT Product Docs (PD):   (was: New)
             EAP PT Test Dev (TD):   (was: TODO)
        EAP PT Docs Analysis (DA):   (was: TODO)
            EAP PT Test Plan (TP):   (was: TODO)
    EAP PT Analysis Document (AD):   (was: TODO)


> Add option to route log messages based on the current thread's class loader
> ---------------------------------------------------------------------------
>
>                 Key: WFCORE-4807
>                 URL: https://issues.redhat.com/browse/WFCORE-4807
>             Project: WildFly Core
>          Issue Type: Feature Request
>          Components: Logging
>            Reporter: James Perkins
>            Assignee: James Perkins
>            Priority: Major
>
> Currently any modules that log generally log onto the system log context. In some cases, see  WFCORE-3376, loggers in modules may be created on the wrong log context. This means logs may be routed to the wrong log context.
> LOGMR-264 can introduce a way to route log messages based on the log context. This would allow messages from modules to be routed to deployment specific log contexts. It would also introduce a change in behavior which is the reason for an RFE. A new attribute should be introduce to disable the new routing and allow the old behavior.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)