[
https://issues.apache.org/jira/browse/CXF-7000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15428018#comment-15428018
]
Christian Schneider commented on CXF-7000:
------------------------------------------
I think we should not name the property and variable livelogging. I think this
term is only meaningful inside this discussion.
As the default of this property is to log if it does not exist I would name it
"org.apache.cxf.logging.disable" and the corresponding variable disableLogging.
I think it is more common to have a null value to represent false. If no one
objects I can change this.
I definitely favour keeping it in the existing loggers instead of creating new
interceptors.
About the new logging I am not sure how to combine this with the logger
configs. Should disableLogging have priority or the logging config?
Honestly I think it is a bit confusing to have this property. The logger config
already allows to configure the logging per service and at runtime. So I still
think the same could maybe be achieved by changing the logger config in the
running system.
> Allow logging to be enabled on-the-fly
> --------------------------------------
>
> Key: CXF-7000
> URL: https://issues.apache.org/jira/browse/CXF-7000
> Project: CXF
> Issue Type: Improvement
> Components: Core, logging
> Affects Versions: 3.1.7
> Reporter: Ingo Weiss
>
> Allow the logging feature to be enabled on-the-fly without restarting the bus.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
