[jira] [Commented] (CAMEL-14172) setting loggingSizeLimit to -1 when using CXF components does not disable the size limit as the docs say

["Andrea Cosentino (Jira)" <ji...@apache.org>]

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

Andrea Cosentino commented on CAMEL-14172:
------------------------------------------

You're welcome to work on the fix. I don't remember why it wasn't merged.

This is the situation on master

[https://github.com/apache/camel/blob/master/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfEndpoint.java#L322]

> setting loggingSizeLimit to -1 when using CXF components does not disable the size limit as the docs say
> --------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-14172
>                 URL: https://issues.apache.org/jira/browse/CAMEL-14172
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-cxf
>    Affects Versions: 2.24.2
>            Reporter: David Schlenk
>            Priority: Trivial
>
> The docs for the CXF component claim that setting the value of option *loggingSizeLimit* to -1 will disable the size limit. This is not the case - when using -1, the default size limit is still in place. CAMEL-9102 theoretically fixes this issue, but seems to have been closed without merging the PR. Happy to provide a new PR that does similar against current, but it would be nice if either the docs were changed or the bug gets fixed to do what the docs say.



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