[
https://issues.apache.org/jira/browse/CXF-7000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15424797#comment-15424797
]
Sergey Beryozkin edited comment on CXF-7000 at 8/17/16 4:04 PM:
----------------------------------------------------------------
Yes, the property approach was proposed (such property already exists - but it
is only supported to bootstrap LoggingFeature for now) and in the end we agreed
with Ingo delaying adding a dedicated utility support like bus.setLiveLogging().
But the observation about the code having to be recompiled/changed whenever the
dynamic requirements change (even if we simply do bus.setProperty("...")) is
valid.
Ingo how do you plan to use such a would be 'bus.setLiveLogging(true/false)'
method ?
I can imagine a code (in the client or in some custom interceptor sitting in
front of LoggingIn/OutInterceptor) that reacts to external notifications (ex,
from the management console) which will either turn the live logging either on
or off. Example, the console receives a red flag event that something is not
right and Admin presses a Button like "Live Log ON" and immediately the logging
goes ON (per-whatever logging configuration) - and once the issue is sorted -
Admin presses "Live Log OFF" - the logging is OFF. This would work for me as
far as having a generic code immune to the log requirement changes, but I
wonder how realistic such a scenario is.
was (Author: sergey_beryozkin):
Yes, the property approach was proposed (such property already exists - but it
is only supported to bootstrap LoggingFeature for now) and in the end we agreed
with Ingo delaying adding a dedicated utility support like bus.setLiveLogging().
But the observation about the code having to be recompiled/changed whenever the
dynamic requirements change (even if if simply do bus.setProperty("...")) is
valid.
Ingo how do you plan to use such a would be 'bus.setLiveLogging(true/false)'
method ?
I can imagine a code (in the client or in some custom interceptor sitting in
front of LoggingIn/OutInterceptor) that reacts to external notifications (ex,
from the management console) which will either turn the live logging either on
or off. Example, the console receives a red flag event that something is not
right and Admin presses a Button like "Live Log ON" and immediately the logging
goes off (per-whatever logging configuration) - and once the issue is sorted -
Admin presses "Live Log OFF". This would work for me as far as having a generic
code immune to the log requirement changes, but I wonder how realistic such a
scenario is.
> 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)
