You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Matt Sicker (JIRA)" <ji...@apache.org> on 2014/05/26 02:27:01 UTC
[jira] [Commented] (LOG4J2-653) Add plugin builder classes as
alternative to factory methods.
[ https://issues.apache.org/jira/browse/LOG4J2-653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14008498#comment-14008498 ]
Matt Sicker commented on LOG4J2-653:
------------------------------------
I have an example of what could be done in PatternLayout right now.
> Add plugin builder classes as alternative to factory methods.
> -------------------------------------------------------------
>
> Key: LOG4J2-653
> URL: https://issues.apache.org/jira/browse/LOG4J2-653
> Project: Log4j 2
> Issue Type: Improvement
> Components: Core
> Reporter: Matt Sicker
> Assignee: Matt Sicker
> Labels: config
>
> It would be useful to have builder-style classes as an alternative to plugin factory methods. This would be useful in two settings:
> # Easier to construct plugins in tests and in the code.
> # Can add annotations to fields for value injection in the PluginBuilder class.
> This could replace the existing factory methods, or it could complement it. This would also make it easier to support programmatic configuration.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org