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 "Ralph Goers (JIRA)" <ji...@apache.org> on 2012/07/11 22:13:35 UTC
[jira] [Closed] (LOG4J2-20) log4j 2 should have clean separation of
configuration from function
[ https://issues.apache.org/jira/browse/LOG4J2-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralph Goers closed LOG4J2-20.
-----------------------------
Closing since there have been no updates to this issue since it was marked resolved.
> log4j 2 should have clean separation of configuration from function
> -------------------------------------------------------------------
>
> Key: LOG4J2-20
> URL: https://issues.apache.org/jira/browse/LOG4J2-20
> Project: Log4j 2
> Issue Type: Test
> Reporter: Curt Arnold
> Assignee: Ralph Goers
> Fix For: 2.0-alpha1
>
>
> log4j 1.2 does not enforce a clean separation between configuration and service provision. Some configuration changes take effect immediately, some only on a call to activateOptions and rarely are they appropriately synchronized with the service provision. log4j 2.0 should have services provided by immutable or at least not externally immutable objects and keep configuration in distinct classes that construct the service providing instance and then replace the existing service with proper synchronization.
> This is related to prefer immutable classes
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org