camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Wash (JIRA)" <>
Subject [jira] [Commented] (CAMEL-5651) Control Bus EIP
Date Tue, 30 Oct 2012 17:44:15 GMT


Chris Wash commented on CAMEL-5651:

My client is requesting this... 

Agreed that the big outstanding question is around message format, if it can be standardized.
 Spring Integration does support this EIP - but I haven't looked at the implementation.  To
the extent that the command syntax can align with any exposed JMX capabilities would be a
plus in my view - cohesion between the two interfaces would be a big plus in my book.
> Control Bus EIP
> ---------------
>                 Key: CAMEL-5651
>                 URL:
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-core, eip
>            Reporter: Claus Ibsen
>             Fix For: Future
> Control Bus EIP
> I think we should consider a control bus EIP (eg implemented as a component).
> Then people can manage their Camel apps by sending messages to a control bus endpoint.
> For example to
> - start a route
> - stop a route
> - get statistics
> - shutdown camel (???)
> eg a bit like what you can do with JMX management, but over Camel endpoint.
> To trick would be to find a message format the control bus can parse. For example should
we use a header for the command.
> But that also makes it easier for people to start|stop a route from a route. Now just
send a message to an endpoint, for example using wire tap.
> {code}
> from x
>   to y
>   wire tap ("controlbus:action=start-route&param=route2")
> {code}
> Would need to give some more thought about the syntax and what to be supported by the
control bus.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message