[ 
https://issues.apache.org/jira/browse/LOG4J2-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426479#comment-16426479
 ] 

ASF GitHub Bot commented on LOG4J2-2307:
----------------------------------------

GitHub user cakofony opened a pull request:

    https://github.com/apache/logging-log4j2/pull/162

    LOG4J2-2307: MutableLogEvent memento retains format string

    MementoLogEvent provides the original format string and parameters
    in addition to the formatted text.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/cakofony/logging-log4j2 memento_message

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/logging-log4j2/pull/162.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #162
    
----
commit 39b82e15fde0cb64bbff04a610818219383ae9bc
Author: Carter Kozak <ckozak@...>
Date:   2018-04-03T03:49:09Z

    LOG4J2-2307: RingBufferLogEvent and MutableLogEvent memento to 
MementoLogEvent
    
    MementoLogEvent provides the original format string and parameters
    in addition to the formatted text.

----


> Reusable event memento messages should retain format
> ----------------------------------------------------
>
>                 Key: LOG4J2-2307
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2307
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.11.0
>            Reporter: Carter Kozak
>            Assignee: Carter Kozak
>            Priority: Major
>
> Currently MutableLogEvent and RingBufferLogEvent memento implementations 
> create ParameterizedMessage instances using the formatted message string and 
> a copy of the parameter array.
> We can use a "MementoMessage" type with fields for both references to the 
> formatted message and the message format, as well as parameters.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to