camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-7136) Add API to make it easier to control lifecycle of @Consumer which are not Camel routes
Date Thu, 16 Jan 2014 07:57:19 GMT

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

Claus Ibsen commented on CAMEL-7136:
------------------------------------

And also the control bus component should be able to do so as well
http://camel.apache.org/controlbus.html

> Add API to make it easier to control lifecycle of @Consumer which are not Camel routes
> --------------------------------------------------------------------------------------
>
>                 Key: CAMEL-7136
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7136
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-core
>            Reporter: Claus Ibsen
>             Fix For: 3.0.0, Future
>
>
> See nabble
> http://camel.465427.n5.nabble.com/starting-and-stopping-routes-created-via-spring-and-Consume-tp5745973.html
> When you use @Consume on a bean, then a consumer is created to consume from the endpoint
and invoke the method on the bean. We should have an API in CamelContext so end users easily
can control the lifecycle of these, such as stopping/pausing/resuming/starting them. Just
as you can do with routes today.
> A @Consume does not create a route, and hence not so easy to control. 
> There is also Karaf commands we should have for doing this as well. And a JMX API exposed.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message