[
https://issues.apache.org/jira/browse/LOG4J2-2491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16669021#comment-16669021
]
Gary Gregory commented on LOG4J2-2491:
--------------------------------------
The only consequence that I can see is that all filterable objects like
appenders have an additional instance variable slot, which will by default
point to an empty array (or null.)
The properties are meant to be used for programmatic access, whether from Java,
XSLT, or whatever. Tools and programs can generate Log4j configuration files
that contain {{Property}} elements which then can further be examined and
processed by other programs and tools at install time for apps and also at
runtime to drive behavior.
WRT white-space, I am not sure what happened, is this a change from tabs to
spaces or the other way around?
> Allow all Appenders to optionally carry a Property array
> --------------------------------------------------------
>
> Key: LOG4J2-2491
> URL: https://issues.apache.org/jira/browse/LOG4J2-2491
> Project: Log4j 2
> Issue Type: New Feature
> Components: Appenders
> Reporter: Gary Gregory
> Assignee: Gary Gregory
> Priority: Major
> Fix For: 3.0.0, 2.11.2
>
>
> Allow all Appenders to optionally carry a Property array. This allows 3rd
> party tooling to read and write properties for their own use.
> This refactoring pulls up the {{properties}} instance variable and methods
> from {{org.apache.logging.log4j.kafka.appender.KafkaAppender.Builder}} to
> {{org.apache.logging.log4j.core.filter.AbstractFilterable.Builder}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
