logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remko Popma (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (LOG4J2-1660) ThreadContext to expose ReadOnlyThreadContextMap internal data structure
Date Thu, 03 Nov 2016 14:57:58 GMT

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

Remko Popma closed LOG4J2-1660.
-------------------------------
    Resolution: Fixed

Fixed in master.

Added public method {{ThreadContext::getThreadContextMap}}, removed class {{ThreadContextAccess}}.


> ThreadContext to expose ReadOnlyThreadContextMap internal data structure 
> -------------------------------------------------------------------------
>
>                 Key: LOG4J2-1660
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1660
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: API
>            Reporter: Remko Popma
>            Assignee: Remko Popma
>             Fix For: 2.8
>
>
> Add public method {{ThreadContext::getThreadContextMap}} that returns a {{ReadOnlyThreadContextMap}}
view of the internal data structure. 
> This method will be used by the log4j-core ContextInjectors so the ThreadContextAccess
class in the org.apache.logging.log4j package in log4j-core can be removed.
> Furthermore this method can be used as a building block by SPI implementators.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
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