Claus Ibsen-2 wrote: > >> >> Is there an easy way to know if all components/processors in a >> CamelContext >> are started? I can easily get the CamelContext injected into the >> producer >> bean, but I'm not sure what components I would need to check isStarted on >> before sending a message. > Yeah I guess you can check the camel context itself if its started. > There where some changes recently regarding this. Might work better in > 1.6.1+. > There is a JIRA Ticket somewhere on this. Dont have time to find it. > I think you're referring to this JIRA issue: http://issues.apache.org/activemq/browse/CAMEL-1509 If I understand correctly the meaning of "isStarted" on a camel context was fixed up so "isStarted" is false while "isStarting" is true.
It seems strange to me that a spring-injected camel resource like ProducerTemplate can be "not started" when it is injected. Aren't injected resources supposed to be ready to go immediately? Does camel inject resources before the context is started for performance reasons? Are there any plans to change this? -- View this message in context: http://www.nabble.com/SEDA-Component-Exception%3A-No-producer%2C-this-processor-has-not-been-started%21-tp23407604p23573062.html Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
