cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Schneider <ch...@die-schneider.net>
Subject Re: default encoding in LoggingInInterceptor
Date Fri, 19 Aug 2016 11:16:15 GMT
Can you open some jiras to document the requirements that are not 
implemented now?
How should logging the binary contents work? As a switch or should we 
simply never log binaries?

Christian

On 19.08.2016 11:42, Sergey Beryozkin wrote:
> Hi Christian
>
> As discussed on IRC, IMHO marking core LoggingInterceptors as 
> deprecated in 3.2.0 (which is what you suggested below) can be very 
> reasonable.
> The problem I've spotted now is that the ext/'new' interceptors do not 
> support some features that the core/'old' interceptors do, which 
> unfortunately shows the problem of having a pair of logging features.
>
> Specifically the core interceptors can avoid logging the binary payloads
> (multiparts/etc) which was a pretty annoying issue for some users - 
> seeing some massive binary blobs logged (and partially due to the log 
> limits) was not good.
>
> IMHO, before the old interceptors can be marked as Deprecated we need 
> to have those features that are available in the core interceptors 
> (such as the one I mentioned) synced to the ext loggers
>
> Cheers, Sergey 

-- 
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com


Mime
View raw message