[
https://issues.apache.org/jira/browse/CAMEL-14172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16972906#comment-16972906
]
David Schlenk commented on CAMEL-14172:
---------------------------------------
[~acosentino] thanks for responding! I've tested this change against the v2
branch IRL and it does fix the issue. I tried my hand at figuring out how to
write a unit test, but I couldn't figure out how to either obtain the
underlying LoggingFeature from the CxfEndpoint to check for its value or
successfully intercept the output to brute force testing that a message longer
than the default worked. Happy to add one if someone can point me in the right
direction, though. [PR #3332|https://github.com/apache/camel/pull/3332].
> 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
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)
