[
https://issues.apache.org/jira/browse/CAMEL-5651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487758#comment-13487758
]
Claus Ibsen commented on CAMEL-5651:
------------------------------------
Yeah the control bus ought to be able to use the management API. That allows
you to control much out of the box then.
Though for people disabling JMX we may offer limited management using the API
on CamelContext to control routes etc.
We should also allow to gather statistics which you can do from the management
API. But in bulk as well.
Then you can do alike ActiveMQ which supports a plugin to gather stats, by
sending a message to a queue.
http://activemq.apache.org/statisticsplugin.html
The SI control bus, is based on executing either a Spring Expression or Groovy
expression, which you send in the message body.
> Control Bus EIP
> ---------------
>
> Key: CAMEL-5651
> URL: https://issues.apache.org/jira/browse/CAMEL-5651
> Project: Camel
> Issue Type: New Feature
> Components: camel-core, eip
> Reporter: Claus Ibsen
> Fix For: Future
>
>
> Control Bus EIP
> http://www.eaipatterns.com/ControlBus.html
> 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¶m=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: http://www.atlassian.com/software/jira