Let me clarify: I understand that I can create another component class for
the control channel, and its corresponding endpoint class. But I need the
two types to be able to interact; when I get a control channel message, I
need to be able to register a message filter with the dynamic router
compon
Hi, Claus. I am going with your suggestion to create a separate endpoint
for the control channel. I am having a little trouble being able to create
the endpoint for the control channel. Camel is complaining that "No
endpoint could be found for: dynamic-router-control://, please check your
classp
Hi
No this is not really how an endpoint is designed. Each endpoint is
responsible for creating its consumer/producers.
However a consumer / producer may use some shared entity, such as seda
does with its queues.
Maybe what you are trying is to shoe-horn everything into the same endpoint.
For yo
I have added path params to the URI for certain conditions of my
component. The normal use case would have a URI like:
my-component://name. Now there is another use case where I can specify a
URI like: my-component://name//param. In this case, "action" can
have different values. But I only want
