Yes it does. Thanks for all this information.
Ashwin Karpe wrote:
>
> Hi,
>
> I am not sure I understand the question.
>
> A Camel route is made up of 2 or more endpoints which in its most basic
> form looks like this,
> from("URI in Message Consumer Role").
> to("URI in Message Pro
Hi,
I am not sure I understand the question.
A Camel route is made up of 2 or more endpoints which in its most basic form
looks like this,
from("URI in Message Consumer Role").
to("URI in Message Producer role")
The Consumer URI could be a web service, an http listener or a JMS Queue
l
Thanks Ashwin,
I'm not anticipating the solution will require to work on different
technology stacks as the "Producer" and "Consumer" are internal to the
System.
However, I may have to expose the consume side of the functionality as a Web
Service later. Do you think I'll be able to leverage anyt
Hi,
Camel is primarily a router surrounded by other capabilities (processors,
interceptors etc). Camel mediates between 2 or more technology endpoints and
applies rules, transforms, integration patterns along the way.
Asynchronous behavior primarily involves setting up listeners backed by an
eve
