[jira] Commented: (LOG4J2-20) log4j 2 should have clean separation of configuration from function

["Ralph Goers (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LOG4J2-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12867812#action_12867812 ] 

Ralph Goers commented on LOG4J2-20:
-----------------------------------

In my experimental branch the configuration is separate from the loggers returned via LogManager.getLogger(). Once the configuration is active new Loggers (actually LoggerConfig objects) cannot be added to the configuration. Creating a new configuration is done in such a way that Loggers are never in an unconfigured state.  However, adding a new Appender or Filter can be done as these operations can be performed safely.

> 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
>
> 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.
-
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