I think it might be because 202 is handled by a oneway processor and the outbound chain is not invoked though I might be wrong...

Sergey
On 29/12/15 11:17, Sergey Maslov wrote:
The issue is reproduced for with 202 - Accepted http status.

On Tue, Dec 29, 2015 at 1:28 PM, Sergey Maslov <therealma...@gmail.com>
wrote:

Hi!
I need to log imcoming requests with corresponsing responses.
According
I add custom LoggingFeature and implement LogEventSender interface.
The messages log fine except messages with emtpty body and
containing http status code only (these are the responses to the service).
According the contract, these messages are needed to be sent.
How could I log them?

--
*Sergey Maslov*






--
Sergey Beryozkin

Talend Community Coders
http://coders.talend.com/

Reply via email to