[
https://issues.apache.org/jira/browse/CAMEL-13903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16914355#comment-16914355
]
Peter Palaga commented on CAMEL-13903:
--------------------------------------
I agree this is not an issue from the Camel point of view. The issue exists
solely on the side of Camel Quarkus, where the CXF REST client does not work
out of the box in the native mode on Quarkus. The exact error messages can be
seen in https://github.com/apache/camel-quarkus/issues/74 .
Solving those issues in the CXF REST client is perhaps possible, but from our
(camel-quarkus) point of view not preferred, because it is much more work than
somehow switching the REST client implementation in the telegram component.
So if simply replacing the CXF client with the RestEasy one does not find
enough acceptance on the Camel side, let me try to find some other option and
propose it here.
> Port telegram component to RestEasy
> -----------------------------------
>
> Key: CAMEL-13903
> URL: https://issues.apache.org/jira/browse/CAMEL-13903
> Project: Camel
> Issue Type: Wish
> Components: camel-telegram
> Reporter: Peter Palaga
> Priority: Major
>
> This is motivated by our efforts to port the telegram component to Quarkus
> where RestEasy is available out of the box.
> https://github.com/apache/camel-quarkus/issues/74
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
