reta commented on code in PR #3343:
URL: https://github.com/apache/cxf/pull/3343#discussion_r3692680758


##########
rt/features/logging/src/main/java/org/apache/cxf/ext/logging/AbstractLoggingInterceptor.java:
##########
@@ -25,20 +25,21 @@
 import java.util.regex.Pattern;
 
 import org.apache.cxf.common.util.PropertyUtils;
-import org.apache.cxf.ext.logging.event.DefaultLogEventMapper;
-import org.apache.cxf.ext.logging.event.LogEvent;
-import org.apache.cxf.ext.logging.event.LogEventSender;
-import org.apache.cxf.ext.logging.event.PrettyLoggingFilter;
+import org.apache.cxf.ext.logging.event.*;
 import org.apache.cxf.interceptor.Fault;
 import org.apache.cxf.message.Exchange;
 import org.apache.cxf.message.Message;
 import org.apache.cxf.phase.AbstractPhaseInterceptor;
 
+import static 
org.apache.cxf.ext.logging.event.DefaultLogEventMapper.normalizeFlow;
+
 public abstract class AbstractLoggingInterceptor extends 
AbstractPhaseInterceptor<Message> {
     public static final int DEFAULT_LIMIT = 48 * 1024;
     public static final int DEFAULT_THRESHOLD = -1;
     public static final String CONTENT_SUPPRESSED = "--- Content suppressed 
---";
     protected static final String  LIVE_LOGGING_PROP = 
"org.apache.cxf.logging.enable";
+    protected static final String IDEMPOTENT_LOGGING_PROP = 
"org.apache.cxf.idempotent.logging."; // the EventType (flow) and ExchangeId 
will be concatenated

Review Comment:
   Thanks for the pull request @vp340 , I would advice against introducing yet 
another property, not only it becomes very confusing, it also difficult to 
figured out where all these different properties are coming from. I will try to 
spend some time looking into the problem, if you could attach a simple 
reproducer to the JIRA ticket, that would be great to understand the issue in 
context. Thank you. 



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to