[
https://issues.apache.org/jira/browse/LOG4J2-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607245#action_12607245
]
Ralph Goers commented on LOG4J2-9:
----------------------------------
I am in favor of leveraging Spring for wiring components together. I'm less
clear on whether we want to expose it through to the components that have in
the past been wired in via the log4j configuration. My first reaction is that
it would be OK to allow Appenders, Layouts, etc as Spring beans, but not
Loggers. However, if someone has a convincing argument to why everything should
be configured via Spring I'm sure I could be convinced.
It seems to me that we need fundamental agreement on whether or not to leverage
Spring before we move on.
> log4j 2.0 should leverage existing (preferably ASF) configuration frameworks
> ----------------------------------------------------------------------------
>
> Key: LOG4J2-9
> URL: https://issues.apache.org/jira/browse/LOG4J2-9
> Project: Log4j 2
> Issue Type: Wish
> Components: Configurators
> Reporter: Curt Arnold
>
> log4j 2.0 should avoid implementing its own configuration framework in
> preference to being compatible with commonly used configuration frameworks
> and services. Compatibility with existing log4j 1.2 configuration files
> might be accomplished by XSLT transforms that convert the legacy format into
> the equivalent with the selected configuration framework. log4j 2.0 should
> be readily configurable with JMX and a JMX centric design for configuration
> may be desirable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
