You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2020/05/14 08:02:00 UTC
[jira] [Resolved] (CAMEL-15057) camel-telegream -
NullPointerException with telegram webhook
[ https://issues.apache.org/jira/browse/CAMEL-15057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-15057.
---------------------------------
Fix Version/s: 3.4.0
Resolution: Fixed
Thanks for reporting, the PR and testing my PR. Good we found a solution.
> camel-telegream - NullPointerException with telegram webhook
> ------------------------------------------------------------
>
> Key: CAMEL-15057
> URL: https://issues.apache.org/jira/browse/CAMEL-15057
> Project: Camel
> Issue Type: Bug
> Components: camel-telegram, camel-webhook
> Affects Versions: 3.2.0
> Reporter: Zheng Feng
> Assignee: Zheng Feng
> Priority: Major
> Fix For: 3.4.0
>
>
> This issue comes across [camel-quarkus issue #1200 |https://github.com/apache/camel-quarkus/issues/1200]. The following router
> {code:java}
> from("webhook:telegram:bots")
> .log("${body}");
> {code}
> which is added before the camel context is started. So the doStart() in the TelegramEndpoint is deferred and that causes the WebHookEndpoint invokes the registerWebhook() throws NPE.
> It could be considered to move the codes to the doInit() which seems safer as this can also happens outside quarkus etc
--
This message was sent by Atlassian Jira
(v8.3.4#803005)