[
https://issues.apache.org/jira/browse/LOG4J2-1438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15338496#comment-15338496
]
Remko Popma commented on LOG4J2-1438:
-------------------------------------
Yes, with hindsight that is probably what I should have done in the
[ReusableMessage|http://logging.apache.org/log4j/2.x/log4j-api/xref/org/apache/logging/log4j/message/ReusableMessage.html]
interface instead of the {{Object[] swapParameters(Object[]
emptyReplacement)}} method...
> Add method getParameter() to ObjectMessage (and ReusableObjectMessage)
> ----------------------------------------------------------------------
>
> Key: LOG4J2-1438
> URL: https://issues.apache.org/jira/browse/LOG4J2-1438
> Project: Log4j 2
> Issue Type: Improvement
> Components: API
> Affects Versions: 2.6, 2.6.1
> Reporter: Remko Popma
> Fix For: 2.7
>
>
> While analysing LOG4J2-1397 I found it is currently not possible for client
> code to get a reference to the Object in the ObjectMessage without creating a
> temporary (single-element) array (returned from {{getParameters()}}.
> This ticket proposes to add a method to the ObjectMessage and
> ReusableObjectMessage interface that gives direct access to the object
> parameter.
> I'm flexible with regards to the name of this new method. I thought of
> {{getParameter()}} but an alternative could be {{getObject()}} or something
> else.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
