[
https://issues.apache.org/jira/browse/CAMEL-14377?focusedWorklogId=368928&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-368928
]
ASF GitHub Bot logged work on CAMEL-14377:
------------------------------------------
Author: ASF GitHub Bot
Created on: 09/Jan/20 10:34
Start Date: 09/Jan/20 10:34
Worklog Time Spent: 10m
Work Description: jamesnetherton commented on pull request #3470:
CAMEL-14377: Add configuration option to enable / disable BraintreeLogHandler
URL: https://github.com/apache/camel/pull/3470
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 368928)
Time Spent: 20m (was: 10m)
> 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)
