[
https://issues.apache.org/jira/browse/CXF-8365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17228785#comment-17228785
]
Freeman Yue Fang commented on CXF-8365:
---------------------------------------
Hi [~cachescrubber],
I'm a bit confused, since your custom MyLoggingInInterceptor extends
org.apache.cxf.ext.logging.LoggingInInterceptor, you actually can override
{code}
public void handleMessage(Message message)
{code}
in org.apache.cxf.ext.logging.LoggingInInterceptor and get any behaviour to
meet your requirement. Or do I miss anything?
Best Regards
Freeman
> LoggingInInterceptor could not be extended / logs only once
> -----------------------------------------------------------
>
> Key: CXF-8365
> URL: https://issues.apache.org/jira/browse/CXF-8365
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime, logging
> Affects Versions: 3.4.0
> Reporter: Lars Uffmann
> Assignee: Freeman Yue Fang
> Priority: Major
>
> Coming with CXF-8257 {{org.apache.cxf.ext.logging.LoggingInInterceptor}} will
> log a given message only once:
> {code:java}
> public void handleMessage(Message message) throws Fault {
> if (isLoggingDisabledNow(message)) {
> return;
> } else {
> //ensure only logging once for a certain message
> //this can prevent message logging again when fault
> //happen after PRE_INVOKE phase(rewind calls into
> LoggingInFaultInterceptor)
> message.put(LIVE_LOGGING_PROP, Boolean.FALSE);
> }
> {code}
> Filtering is done per message, not per Interceptor instance. We use a custom
> {{MyLoggingInInterceptor}} which subclasses the {{LoggingInInterceptor}}. (We
> Subclass in order to use different {{LogEventSender).}} So two distinct
> interceptor instances are applied to the Endpoint/Bus/Client but the message
> is logged only in the first invocation.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
