logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Smith (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LOG4J2-9) log4j 2.0 should leverage existing (preferably ASF) configuration frameworks
Date Mon, 23 Jun 2008 21:43:45 GMT

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

Paul Smith commented on LOG4J2-9:

Just to clear up what I actually meant, I wasn't actually advocating the _use_ of Spring within
log4j, but given how useful and popular Spring is, we should at least factor into the design
something that is IoC friendly.

for example, perhaps so 'spring-extras' companion that obey the Spring Lifecycle interface
to startup/shutdown.

The more difficult objective though for a logging framework is to then _support_ the container
in it's startup routine by allowing useful logging.  Bit of a chicken/egg problem there unless
the log4j configuration can be done as early as possible.

Anyway, I was just voicing that we should probably have a  Spring-like container in mind during
the configuration design.  May even be worth reaching out into the, say, Spring community
for further discussion (or bringing them into this one)

> 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