[jira] [Commented] (CXF-8226) Not able to log webservice calls with corrupt data

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (CXF-8226) Not able to log webservice calls with corrupt data

Colm O hEigeartaigh (Jira)

    [ https://issues.apache.org/jira/browse/CXF-8226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17228798#comment-17228798 ]

Freeman Yue Fang commented on CXF-8226:
---------------------------------------

I believe this is fixed by CXF-8257

> Not able to log webservice calls with corrupt data
> ---------------------------------------------------
>
>                 Key: CXF-8226
>                 URL: https://issues.apache.org/jira/browse/CXF-8226
>             Project: CXF
>          Issue Type: Improvement
>          Components: logging
>    Affects Versions: 3.3.5
>            Reporter: Bernhard Mähr
>            Priority: Major
>
> We are providing a webservice connected by multiple customers with no or not much technical knowledge and existing old software. To support them it would be helpful to be able to log webservice calls which even cant be parsed.
> I have implemented a solution by replacing the OutFaultChainInitiatorObserver with a custom version which logs the in message before continuing.
> {code:java}
> public class MyOutFaultChainInitiatorObserver extends OutFaultChainInitiatorObserver {      
>     @Override
>     public void onMessage(final Message message) {
>         MySlf4jVerboseEventSender.in.handleMessage(message);
>         super.onMessage(message);
>     }
> }
> {code}
> But it is not ea really clean solution. Would be nice if it would be easier to configure/activate. Additionally I think the request is logged twice if it is parsable but fails with an other error. 
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)