[
https://issues.apache.org/jira/browse/LOG4J2-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory resolved LOG4J2-1935.
----------------------------------
Resolution: Fixed
In git master commit 76aff58919dc5030367ea24c7c8ef42dca3b75cd
> Add with(String, primitive) methods to
> org.apache.logging.log4j.message.MapMessage
> ----------------------------------------------------------------------------------
>
> Key: LOG4J2-1935
> URL: https://issues.apache.org/jira/browse/LOG4J2-1935
> Project: Log4j 2
> Issue Type: New Feature
> Reporter: Gary Gregory
> Assignee: Gary Gregory
>
> Add with() methods for primitives and Object:
> - with(String, boolean)
> - with(String, byte)
> - with(String, char)
> - with(String, double)
> - with(String, float)
> - with(String, int)
> - with(String, long)
> - with(String, Object)
> - with(String, short)
> This one already exists:
> - with(String, String)
> This parallels what you can do with a JMS {{MapMessage}}.
> The following {{protected}} methods have also been added:
> - validate(String, boolean)
> - validate(String, byte)
> - validate(String, char)
> - validate(String, double)
> - validate(String, float)
> - validate(String, int)
> - validate(String, long)
> - validate(String, Object)
> - validate(String, short)
> The method {{validate(String, String)}} already exists.
> In 2.8.2, MapMessage managed a Map<String, String>.
> In 2.9:
> - MapMessage is now declared with generics to define what kind of values are
> managed.
> - The new Subclass StringMapMessage is typed specifically to deal with String
> values.
> The StringMapMessage class does not perform any type conversion or checks.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
