[CXF-2596] Default logging in interceptor chain may pollute the log with stacktrace from application exceptions that are a part of the normal flow (should not be logged).

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.1.9, 2.2.6
• Component/s: Configuration

Environment

All

• Assignee: Daniel Kulp
• Reporter: Tomas Majak
• Created: 30/Dec/09 09:04
• Updated: 01/Feb/10 19:02
• Resolved: 06/Jan/10 18:14

Description

A user of CXF may need custom handling for runtime errors produced by the application, not catchable within the application, e.g. exceptions from interceptors to the actual service.
E.g. applications may produce Exceptions that are a normal part of the flow in the application, in that case, it pollutes the log file to have it logged as stacktrace.

background: http://www.mail-archive.com/[e-mail]/msg10976.html

Configure via setting property to Bus or Service:
<property name="org.apache.cxf.logging.FaultLogger">
<bean class="com.foo.MyFaultLogger"/>
</property>

MyFaultLogger must implement org.apache.cxf.logging.FaultLogger

Programatically:
Bus bean = (Bus) applicationContext.getBean("cxf");
bean.setProperty("org.apache.cxf.logging.FaultLogger", myLogger);

By endpoint:
<jaxws:endpoint id="mySericeWS" implementor="#myServiceBean" address="/myServiceWS">
<jaxws:properties>
<entry key="org.apache.cxf.logging.FaultLogger">
<bean class="com.foo.MyFaultLogger"/>
</entry>
</jaxws:properties>
</jaxws:endpoint>