[
https://issues.apache.org/jira/browse/CAMEL-14377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Netherton resolved CAMEL-14377.
-------------------------------------
Resolution: Fixed
> Add configuration option to disable BraintreeLogHandler
> -------------------------------------------------------
>
> Key: CAMEL-14377
> URL: https://issues.apache.org/jira/browse/CAMEL-14377
> Project: Camel
> Issue Type: Improvement
> Components: camel-braintree
> Reporter: James Netherton
> Assignee: James Netherton
> Priority: Minor
> Fix For: 3.1.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The Braintree component has its own JUL-SLF4J bridge class
> [BraintreeLogHandler|https://github.com/apache/camel/blob/master/components/camel-braintree/src/main/java/org/apache/camel/component/braintree/internal/BraintreeLogHandler.java].
> If there's an existing log framework on the classpath that can already do
> such bridging (E.g JBoss Logging on WildFly and Quarkus), then you end with
> an endless recursion situation when Braintree invokes any of its logger
> methods.
> It'd be nice to have the option of disabling BraintreeLogHandler in such
> scenarios.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
