You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Tomas Majak (JIRA)" <ji...@apache.org> on 2009/12/30 10:05:29 UTC
[jira] Created: (CXF-2596) Default logging in interceptor chain may
pollute the log with stacktrace from application exceptions that are a part
of the flow (should not be logged).
Default logging in interceptor chain may pollute the log with stacktrace from application exceptions that are a part of the flow (should not be logged).
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: CXF-2596
URL: https://issues.apache.org/jira/browse/CXF-2596
Project: CXF
Issue Type: New Feature
Components: Configuration
Environment: All
Reporter: Tomas Majak
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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (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).
Posted by "Tomas Majak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomas Majak updated CXF-2596:
-----------------------------
Attachment: custom_logging_in_interceptorchain_ver2.patch
new version after Sergeys comments
> 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).
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CXF-2596
> URL: https://issues.apache.org/jira/browse/CXF-2596
> Project: CXF
> Issue Type: New Feature
> Components: Configuration
> Environment: All
> Reporter: Tomas Majak
> Attachments: custom_logging_in_interceptorchain.patch, custom_logging_in_interceptorchain_ver2.patch
>
>
> 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/users@cxf.apache.org/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>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (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).
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp updated CXF-2596:
-----------------------------
Fix Version/s: 2.1.9
> 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).
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CXF-2596
> URL: https://issues.apache.org/jira/browse/CXF-2596
> Project: CXF
> Issue Type: New Feature
> Components: Configuration
> Environment: All
> Reporter: Tomas Majak
> Assignee: Daniel Kulp
> Fix For: 2.1.9, 2.2.6
>
> Attachments: custom_logging_in_interceptorchain.patch, custom_logging_in_interceptorchain_ver2.patch
>
>
> 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/users@cxf.apache.org/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>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-2596) Default logging in interceptor chain may
pollute the log with stacktrace from application exceptions that are a part
of the flow (should not be logged).
Posted by "Tomas Majak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomas Majak updated CXF-2596:
-----------------------------
Attachment: custom_logging_in_interceptorchain.patch
patch for custom logging in interceptor chain
> Default logging in interceptor chain may pollute the log with stacktrace from application exceptions that are a part of the flow (should not be logged).
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CXF-2596
> URL: https://issues.apache.org/jira/browse/CXF-2596
> Project: CXF
> Issue Type: New Feature
> Components: Configuration
> Environment: All
> Reporter: Tomas Majak
> Attachments: custom_logging_in_interceptorchain.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (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).
Posted by "Tomas Majak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomas Majak updated CXF-2596:
-----------------------------
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/users@cxf.apache.org/msg10976.html
was:
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.
Summary: 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). (was: Default logging in interceptor chain may pollute the log with stacktrace from application exceptions that are a part of the flow (should not be logged).)
> 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).
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CXF-2596
> URL: https://issues.apache.org/jira/browse/CXF-2596
> Project: CXF
> Issue Type: New Feature
> Components: Configuration
> Environment: All
> Reporter: Tomas Majak
> Attachments: custom_logging_in_interceptorchain.patch
>
>
> 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/users@cxf.apache.org/msg10976.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (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).
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-2596.
------------------------------
Resolution: Fixed
Fix Version/s: 2.2.6
Many thanks for this patch. The only realy change I made was to call it a "FaultListener" instead as that's kind of more appropriate.
> 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).
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CXF-2596
> URL: https://issues.apache.org/jira/browse/CXF-2596
> Project: CXF
> Issue Type: New Feature
> Components: Configuration
> Environment: All
> Reporter: Tomas Majak
> Assignee: Daniel Kulp
> Fix For: 2.2.6
>
> Attachments: custom_logging_in_interceptorchain.patch, custom_logging_in_interceptorchain_ver2.patch
>
>
> 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/users@cxf.apache.org/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>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (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).
Posted by "Sergey Beryozkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795278#action_12795278 ]
Sergey Beryozkin commented on CXF-2596:
---------------------------------------
Hi,
The patch looks really fine, thanks. Just wondering, would it make sense to pass a message to a fault logger too, perhaps for it to be able to check the fault mode, or some other info available from the exchange ?
Another thing to consider : would it make sense to indicate to PhaseInterceptorChain that the default fault logging should go ahead after a fault logger has tried to log ? Otherwise a fault logger may also need to do what the default fault logging already does ? Returning a boolean flag is a possible solution but may be there' s a better solution, provided you agree that it is worth addressing it ?
cheers, Sergey
> 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).
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CXF-2596
> URL: https://issues.apache.org/jira/browse/CXF-2596
> Project: CXF
> Issue Type: New Feature
> Components: Configuration
> Environment: All
> Reporter: Tomas Majak
> Attachments: custom_logging_in_interceptorchain.patch
>
>
> 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/users@cxf.apache.org/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>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (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).
Posted by "Tomas Majak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomas Majak updated CXF-2596:
-----------------------------
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/users@cxf.apache.org/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>
was:
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/users@cxf.apache.org/msg10976.html
added how to use.
> 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).
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CXF-2596
> URL: https://issues.apache.org/jira/browse/CXF-2596
> Project: CXF
> Issue Type: New Feature
> Components: Configuration
> Environment: All
> Reporter: Tomas Majak
> Attachments: custom_logging_in_interceptorchain.patch
>
>
> 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/users@cxf.apache.org/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>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (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).
Posted by "Tomas Majak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795291#action_12795291 ]
Tomas Majak commented on CXF-2596:
----------------------------------
Yes, I actually considered both, but I wanted to keep it simple. But as I'm obviously no the only one who consider that useful, I'll include it. Hold for new patch.
> 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).
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CXF-2596
> URL: https://issues.apache.org/jira/browse/CXF-2596
> Project: CXF
> Issue Type: New Feature
> Components: Configuration
> Environment: All
> Reporter: Tomas Majak
> Attachments: custom_logging_in_interceptorchain.patch
>
>
> 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/users@cxf.apache.org/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>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (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).
Posted by "Sergey Beryozkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795316#action_12795316 ]
Sergey Beryozkin commented on CXF-2596:
---------------------------------------
thanks, I believe the patch is really ready to be applied now, but I'd like to wait for some more comments. One thing I'm not sure about is what to do about the author tag in FaultLogger; usually we just apply a patch with thanks to a contributor but Dan may suggest something else...
cheers, Sergey
> 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).
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CXF-2596
> URL: https://issues.apache.org/jira/browse/CXF-2596
> Project: CXF
> Issue Type: New Feature
> Components: Configuration
> Environment: All
> Reporter: Tomas Majak
> Attachments: custom_logging_in_interceptorchain.patch, custom_logging_in_interceptorchain_ver2.patch
>
>
> 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/users@cxf.apache.org/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>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (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).
Posted by "Tomas Majak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795299#action_12795299 ]
Tomas Majak commented on CXF-2596:
----------------------------------
Maybe FaultLogger isn't the best name for this, its more of a subscriber of exceptions with the possibility to interupt normal logging. But I leave naming up to you guys :)
> 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).
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CXF-2596
> URL: https://issues.apache.org/jira/browse/CXF-2596
> Project: CXF
> Issue Type: New Feature
> Components: Configuration
> Environment: All
> Reporter: Tomas Majak
> Attachments: custom_logging_in_interceptorchain.patch, custom_logging_in_interceptorchain_ver2.patch
>
>
> 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/users@cxf.apache.org/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>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (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).
Posted by "Tomas Majak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795319#action_12795319 ]
Tomas Majak commented on CXF-2596:
----------------------------------
Sure, I'll look out for it when applied.
Remove the author tag.
Thanks
Tomas
> 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).
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CXF-2596
> URL: https://issues.apache.org/jira/browse/CXF-2596
> Project: CXF
> Issue Type: New Feature
> Components: Configuration
> Environment: All
> Reporter: Tomas Majak
> Attachments: custom_logging_in_interceptorchain.patch, custom_logging_in_interceptorchain_ver2.patch
>
>
> 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/users@cxf.apache.org/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>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (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).
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp reassigned CXF-2596:
--------------------------------
Assignee: Daniel Kulp
> 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).
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CXF-2596
> URL: https://issues.apache.org/jira/browse/CXF-2596
> Project: CXF
> Issue Type: New Feature
> Components: Configuration
> Environment: All
> Reporter: Tomas Majak
> Assignee: Daniel Kulp
> Attachments: custom_logging_in_interceptorchain.patch, custom_logging_in_interceptorchain_ver2.patch
>
>
> 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/users@cxf.apache.org/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>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.