[
https://issues.apache.org/jira/browse/CAMEL-16978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-16978:
--------------------------------
Priority: Minor (was: Major)
> Unable to configure multiple xchange endpoints with different crypto exchanges
> ------------------------------------------------------------------------------
>
> Key: CAMEL-16978
> URL: https://issues.apache.org/jira/browse/CAMEL-16978
> Project: Camel
> Issue Type: Bug
> Reporter: James Netherton
> Priority: Minor
>
> It seems reasonable to have a route like:
> {code}
> from("direct:binance")
> .to("xchange:binance");
> from("direct:kraken")
> .to("xchange:kraken");
> {code}
> Unfortunately, this only seems possible by creating a dedicated component
> instance for each crypto exchange. The xchange instance is cached in the
> component, so the first endpoint to initialize it 'wins'.
> https://github.com/apache/camel/blob/main/components/camel-xchange/src/main/java/org/apache/camel/component/xchange/XChangeComponent.java#L55-L68
> I guess it should be cached per crypto exchange used on the endpoint(s).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
