You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2012/09/26 16:47:08 UTC

[jira] [Commented] (CAMEL-5651) Control Bus EIP

    [ https://issues.apache.org/jira/browse/CAMEL-5651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13463863#comment-13463863 ] 

Claus Ibsen commented on CAMEL-5651:
------------------------------------

If we go a bit wacky then the control bus, could potential also be used for creating new routes, eg if the message body is an XML representation of a route. Likewise for updating existing route. Eg what we offer over JMX for that, and also what the Camel Karaf commands uses to show routes etc.
                
> 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&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: http://www.atlassian.com/software/jira