[
https://issues.apache.org/jira/browse/LOG4J2-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15223514#comment-15223514
]
Matt Sicker commented on LOG4J2-1323:
-------------------------------------
As for enforcing configuration, I can think of a workaround:
# Make wrapper plugins with the custom validation logic for all plugins that
should be allowed to be used.
# Delete the Log4j2Plugins.dat file from log4j-core.jar so that the standard
plugins aren't accessible from a config file.
This way, only the Log4j2Plugins.dat file from your wrapper jar is used. If
this isn't secure enough (this can still be worked around), then actual code
changes would be required.
> Remove Final Declarations on Many Classes/Methods
> -------------------------------------------------
>
> Key: LOG4J2-1323
> URL: https://issues.apache.org/jira/browse/LOG4J2-1323
> Project: Log4j 2
> Issue Type: Wish
> Components: API, Appenders, Pattern Converters
> Affects Versions: 2.5
> Reporter: Andrew Bernhagen
> Labels: architecture, easyfix, newbie, patch
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Within my organization, I've had to develop a custom appender that
> automatically configures certain properties and a specific layout to tie into
> other initiatives we have tied to logging. Log4j2 made this much more
> difficult than Log4j1 due to the use of final on many classes (e.g. the
> appender implementations) and methods (all pattern layout methods). This has
> made extension overly difficult and filled with a lot of copy and paste that
> I'd rather not have. Is it possible that these could be removed to make it
> easier to extend the existing implementations?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
