[
https://issues.apache.org/jira/browse/CXF-7000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15420804#comment-15420804
]
Sergey Beryozkin commented on CXF-7000:
---------------------------------------
Yes, the idea makes sense. And I see it can work.
But what about simply having the existing logging interceptors updated to check
the existing property:
{code:java}
// adds LoggingFeature if it is not already added
// and makes sure the contextual property is also set
bus.setEnableLogging(true);
// Logging in/out interceptors check this contextual property in their
handleMessage()
bus.setEnableLogging(false);
// only removes the property
{code}
This way we have a consistent treatment of org.apache.cxf.logging.enabled
property without introducing a new wrapper feature which only enables/disables
other feature.
Thoughts ?
> 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)
