You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are having an internal debate about how to make REST calls with Camel Quarkus. Initially, we planned to use Camel Processors with Quarkus REST clients, but we’ve received feedback from developers suggesting that it might be better to directly use Camel HTTP URIs in the routes. Does anyone have experience with this ?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
We are having an internal debate about how to make REST calls with Camel Quarkus. Initially, we planned to use Camel Processors with Quarkus REST clients, but we’ve received feedback from developers suggesting that it might be better to directly use Camel HTTP URIs in the routes. Does anyone have experience with this ?
Beta Was this translation helpful? Give feedback.
All reactions