ppalaga commented on issue #521: Fix #74 Telegram extension URL: https://github.com/apache/camel-quarkus/pull/521#issuecomment-563165902 > > 2. this PR brings RESTEasy and MP Rest Client and it would be better to just use RESTEasy as we had a long discussion about bringing full RESTEasy client support in Quarkus > > No problem, let me try that. I tried that and my conclusion is that it is not worth of doing it. Here is why: Quarkus MP Rest Client (MPRC) extension provides support for MP Rest Client on top of the RestEasy REST client. To ditch the MP Rest Client spec from the game would actually result in repeating most of the things done in MPRC extension. I do not think we want to do that. The MP Rest Client brings minimal overhead and porting RestEasy REST client separately is too much work that would not pay back. Maybe I should explain why the current proposal depends both on the MP REST client and some RestEasy bits: the RestEasy bits are there for the multipart stuff, that the MP REST client API does not handle in any way. Now I'd try to implement Telegram without CXF or RestEasy, taking some HTTP client and Jackson. Does anybody want to veto it (and name reasons) before I start?
---------------------------------------------------------------- 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: us...@infra.apache.org With regards, Apache Git Services
