[
https://issues.apache.org/jira/browse/CXF-2383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-2383.
------------------------------
Resolution: Won't Fix
Fix Version/s: Invalid
Assignee: Daniel Kulp
The LoggingInInterceptor has completely changed so a point where this is no
longer applicable. Plus, we DON'T want to do this normally as this would keep
larger chunks of information and strings in memory much longer than they should
be.
> Give access to the LoggingMessage object in the Message content.
> ----------------------------------------------------------------
>
> Key: CXF-2383
> URL: https://issues.apache.org/jira/browse/CXF-2383
> Project: CXF
> Issue Type: Improvement
> Components: Core
> Reporter: Rémi Flament
> Assignee: Daniel Kulp
> Priority: Minor
> Fix For: Invalid
>
> Attachments: LoggingInInterceptor.java.patch
>
>
> I need to write an interceptor that store soap messages that cause a fault.
> A way to do it is to implement the handleFault method in an interceptor that
> extends LoggingInInterceptor.
> In the handleFault method I need to access to the LoggingMessage which was
> created by the handleMessage method.
> To achieve this, I've just added the LoggingMessage in the content of the
> Message :
> message.setContent(LoggingMessage.class, buffer);
> Patch attached.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
