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-1438) Add method getParameter() to ObjectMessage (and ReusableObjectMessage)
Date Mon, 01 Aug 2016 15:04:20 GMT

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

Remko Popma closed LOG4J2-1438.
    Resolution: Fixed

Added @since 2.7 javadoc.

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

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message