By providing a StringMap interface that allows Object values we unlocked
numerous custom extensions that the previous Map interface did
not allow.
However the public API should probably stay restricted to String values, at
least for now. This is to prevent memory leaks in web applications: in
We also still use code that we deprecated...
On Tue, Oct 18, 2016 at 8:46 AM, Mikael Ståldal
wrote:
> As part of https://issues.apache.org/jira/browse/LOG4J2-1447 we added
> support for non-String values in log event's context data (with the
> org.apache.logging.log4j.util.StringMap interface).
As part of https://issues.apache.org/jira/browse/LOG4J2-1447 we added
support for non-String values in log event's context data (with the
org.apache.logging.log4j.util.StringMap interface).
However, as far as I can see, we do not leverage the possibility to use
non-String values anywhere. Do we ha
