[
https://issues.apache.org/jira/browse/CAMEL-13263?focusedWorklogId=212285&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-212285
]
ASF GitHub Bot logged work on CAMEL-13263:
------------------------------------------
Author: ASF GitHub Bot
Created on: 13/Mar/19 09:09
Start Date: 13/Mar/19 09:09
Worklog Time Spent: 10m
Work Description: oscerd commented on pull request #2795: [CAMEL-13263]
Lenient IPFS connection check on startup
URL: https://github.com/apache/camel/pull/2795
----------------------------------------------------------------
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: 212285)
Time Spent: 0.5h (was: 20m)
> Lenient IPFS connection check on startup
> ----------------------------------------
>
> Key: CAMEL-13263
> URL: https://issues.apache.org/jira/browse/CAMEL-13263
> Project: Camel
> Issue Type: Task
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
> Priority: Major
> Fix For: 3.0.0, 2.23.2, 2.24.0, 3.0.0-M2
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> 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)
