I have pushed up an update with the internal control channel:
https://github.com/Steve973/camel/tree/CAMEL-17154/components%2Fcamel-dynamic-router
I would love some feedback, if possible, whenever anyone has some time
after the holidays, or whenever.
On Thu, Dec 23, 2021, 10:46 PM Steve973
The code that is currently pushed up to my fork uses the seda component for
the control channel, and a @Consume annotated method in the component
class. While this worked fine and served the purpose, I have not been
satisfied that it is the best solution. So, like you suggested, I am using
the
What you can do is for your component to have a way to send "control"
messages to it that it understands, then users can do
from xxx
to acme:control?action=foo=bar
On Thu, Dec 23, 2021 at 3:19 PM Claus Ibsen wrote:
>
> On Thu, Dec 23, 2021 at 2:21 PM Steve973 wrote:
> >
> > Hello. It
On Thu, Dec 23, 2021 at 2:21 PM Steve973 wrote:
>
> Hello. It appears that the control bus component can only be used for two
> commands (route and language), and for routes, you can only specify an
> action (start, stop, etc). What if we have a component that could also
> benefit from
Hello. It appears that the control bus component can only be used for two
commands (route and language), and for routes, you can only specify an
action (start, stop, etc). What if we have a component that could also
benefit from management messages? Would it make sense to have a third
command
