RE: Log empty message (with HTTP status code only)

ache.org > Subject: Re: Log empty message (with HTTP status code only) > > Sergey, thank you. > But how could I log the fact of 202 response? > > Segery Maslov > > On Tue, Dec 29, 2015 at 11:55 PM, Sergey Beryozkin > <sberyoz...@gmail.com> > wrote: > > &g

Re: Log empty message (with HTTP status code only)

Sergey, thank you. But how could I log the fact of 202 response? Segery Maslov On Tue, Dec 29, 2015 at 11:55 PM, Sergey Beryozkin wrote: > 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... >

Re: Log empty message (with HTTP status code only)

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

Re: Log empty message (with HTTP status code only)

I'm not sure right now, perhaps Aki or Dan may have an idea. May be you can register a custom Log interceptor, after LoggingInInterceptor, that will check CXF message if it is one way (there has to be some property set in the message) and log only if it is oneway... Cheers, Sergey On

Re: Log empty message (with HTTP status code only)

The issue is reproduced for with 202 - Accepted http status. On Tue, Dec 29, 2015 at 1:28 PM, Sergey Maslov wrote: > Hi! > I need to log imcoming requests with corresponsing responses. > According > I add custom LoggingFeature and implement LogEventSender interface. >

Log empty message (with HTTP status code only)

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