[
https://issues.apache.org/jira/browse/CAMEL-13903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16991530#comment-16991530
]
Peter Palaga commented on CAMEL-13903:
--------------------------------------
Some discussions happened in https://github.com/apache/camel-quarkus/pull/521 .
The PR basically contains a new RestEasy and MicroProfile Rest Client based
implementation of the Telegram component.
There is an agreement that we want to maintain as little Telegram code as
possible in Camel Quarkus (in favor of Camel).
I questioned whether we want to make the component pluggable to allow for
running with both CXF and RestEasy REST client, thus having to support two
equivalent rest clients. That's more code, more bugs and more maintenance than
having just one client.
Just switching from CXF to RestEasy in Camel was rejected at least by
[~lburgazzoli]: bringing dependencies tailored to a specific platform may turn
out to be a pain in the long term, because Camel needs to continue working on
spring, karaf and eap. That's a persuasive argument for me.
[~acosentino] said
bq. The problem is just: are we doing this to support telegram on Quarkus? Or
are we doing this because there is an improvement in the component? If the
answer is the first, then we are doing things wrong. The original issue was
opened as "this is not working on Quarkus, lets change from CXF to Resteasy"
and, frankly, this is not a good reason for changing something that works.
Also, it should be the opposite, camel-quarkus should make it work on Quarkus
and the component in Camel should remain exactly the same. I think it's just a
matter of priorities. Quarkus is just one of the platform we cover, it's not
the only platform we need to cover.
I think it is legitimate for a subproject to propose changes, as long as they
do not harm the ecosystem. I am far from wanting to dictate something. I am
interested in finding a solution that is acceptable for all.
My proposal to implement Telegram without CXF or RestEasy, using just some HTTP
client and Jackson found some support.
Let's cont. the discussion here.
> camel-telegram - Allow to plugin JAX-RS client such as resteasy
> ---------------------------------------------------------------
>
> Key: CAMEL-13903
> URL: https://issues.apache.org/jira/browse/CAMEL-13903
> Project: Camel
> Issue Type: New Feature
> Components: camel-telegram
> Reporter: Peter Palaga
> Priority: Major
> Fix For: 3.x
>
>
> 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.4#803005)
