Thanks JB. I got it.
Alex
On Mon, Dec 7, 2020 at 1:40 AM Jean-Baptiste Onofre wrote:
> Hi,
>
> It depends of the features you need and the dependencies.
>
> For instance, Camel Jetty is "large" but provide a good set of features
> (it’s used internally in some other components like the
Thanks Claus. I got it.
Alex
On Mon, Dec 7, 2020 at 1:46 AM Claus Ibsen wrote:
> On Mon, Dec 7, 2020 at 7:40 AM Jean-Baptiste Onofre
> wrote:
> >
> > Hi,
> >
> > It depends of the features you need and the dependencies.
> >
> > For instance, Camel Jetty is "large" but provide a good set of
Hi Alex,
there are many things to consider aside from performance, most notably
the ergonomics of using and later maintaining / troubleshooting issues
All of these components provide good overall performance, with some
exceptions and the amount of tuning one is willing to perform.
My goto
On Mon, Dec 7, 2020 at 7:40 AM Jean-Baptiste Onofre wrote:
>
> Hi,
>
> It depends of the features you need and the dependencies.
>
> For instance, Camel Jetty is "large" but provide a good set of features (it’s
> used internally in some other components like the salesforce one).
>
Do not use
Hi,
It depends of the features you need and the dependencies.
For instance, Camel Jetty is "large" but provide a good set of features (it’s
used internally in some other components like the salesforce one).
Regards
JB
> Le 4 déc. 2020 à 22:00, Alex Luo a écrit :
>
> Hi Dear,
>
> I am
Hi Dear,
I am writing a Camel application which is using Camel component to expose
Http endpoint (Http Consumer), and connect to third party Web Server (Http
Producer).
1) From my readings I have this list of Camel components I can use as Http
Consumer. They all offer the same functionalities
Hi Dear,
I am writing a Camel application which is using a Camel component to expose
Http endpoint (Http Consumer), and connect to a third party Web Server
(Http Producer).
1) From my readings I have this list of Camel components I can use as Http
Consumer. They all offer the same
