[
https://issues.apache.org/jira/browse/CXF-7000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15422661#comment-15422661
]
Sergey Beryozkin commented on CXF-7000:
---------------------------------------
Let me clarify.
Consider a typical case where a LoggingFeature is bootstrapped in CXF (many
options exist). Lets assume it a server.
Now we have (with your proposed PR):
1. The client posts some data - Logging interceptors log the 'live' in/out data
in the console for the debugging purpose
2. bus.setLiveLogging(false)
3. The client posts some more data - Logging interceptors keep logging the
'live' in/out data despite a typed call switching it off
4. bus.setLiveLogging(true)
5. The client posts even more data - Logging interceptors keep logging the
'live' in/out data followed by new 'live' logging interceptors duplicating what
the already installed logging interceptors do
I appreciate you may have a different vision of what the live logging is but
IMHO we can not introduce a *typed* dedicated Bus method to support it. You can
easily add your own utility code doing exactly what you do with the
bus.setLiveLogging() in PR.
I'd like to keep this issue open though to discuss if we can agree on the
following supported:
1. The client posts some data - Logging interceptors log the 'live' in/out data
in the console for the debugging purpose
2. bus.setLiveLogging(false)
3. The client posts some more data - no logging in the console
4. bus.setLiveLogging(true)
5. The client posts even more data - Logging interceptors keep logging the
'live' in/out data
> 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)
