[
https://issues.apache.org/jira/browse/CAMEL-13263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16777933#comment-16777933
]
Thomas Diesler commented on CAMEL-13263:
----------------------------------------
In a scenario where a container (e.g. WildFly) starts a the camel context
automatically, this deferred connection behavior would make the difference of
whether the deployment fails/succeeds.
> Improve IPFS connection handling
> --------------------------------
>
> Key: CAMEL-13263
> URL: https://issues.apache.org/jira/browse/CAMEL-13263
> Project: Camel
> Issue Type: Task
> Reporter: Thomas Diesler
> Priority: Major
> Fix For: 2.23.2
>
>
> The IPFS component needs to create a connection to some IPFS node. Currently
> that happens when the endpoint is created, which happens when the
> CamelContext is started.
> I was wondering whether I should defer that until the first endpoint
> invocation occurs. In which case camelctx.start() would succeed and I could
> asked the endpoint whether a connection could be established (e.g.
> Assume.assumeTrue(comp.getIPFSClient().hasConnection()))
> Currently, camelctx.start() will fail when a connection cannot be
> established. Is there a convention on how camelctx.start() should behave when
> a remote connection is needed?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
