logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Curt Arnold (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LOG4J2-9) log4j 2.0 should leverage existing (preferably ASF) configuration frameworks
Date Thu, 19 Jun 2008 21:07:46 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606558#action_12606558

Curt Arnold commented on LOG4J2-9:

On Jun 19, 2008, at 3:58 PM, Jess Holle wrote:

I'd also add that as long as log4j is going to continue to support multiple LoggerRepository's
per JVM the log4j JMX must fully support this.

The lack of such a capability was the clincher for me not using the existing log4j JMX classes.
 There were other bugs/issues as well.

Beyond this I also really didn't like the fact that various things that are logically data
collections had each element modeled as a JMX attribute.  I'm not against dynamic attributes
-- they make perfect sense for reflection based coverage of Appender and Layout implementations,
but there were cases [whose details I forget, unfortunately], where a logical list of data
was converted into a dynamic attribute set -- to ill effect.  I used child MBeans for such
cases -- which also allowed for broader/deeper configuration coverage.

Jess Holle

> 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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message