The reason is, because you use the bean component in a "from" definition. You can put your two routes together into one.
Christian Sent from a mobile device Am 13.10.2011 21:37 schrieb "Matt Madhavan" <mattmadha...@gmail.com>: > Hello, > Please bear with me as I'm new to Camel. > > I have a my camel snippet as follows: > <camelContext xmlns="http://camel.apache.org/schema/blueprint";> > <route id="in-bound" autoStartup="true"> > <description>Camel In-Bound Route</description> > <from uri="activemq:example.A"/> > <to uri="bean:processMsgService?method=processmsg"/> > </route> > <route id="out-bound" autoStartup="true"> > <description>Camel Out-Bound Route</description> > <from > uri="bean:processMsgService?method=processmsg"/> > <to uri="activemq:example.B"/> > </route> > </camelContext> > > > Event when I do not send any message the bean/method > *uri="bean:processMsgService?method=processmsg"* gets invoked periodically. > > how do I stop this? Looks like activemq:example.A keeps producing null msgs > or the method above always called. > > Any help will be appreciated > > Thanks in advance! > > Matt > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/Camel-Active-MQ-Queue-Stopping-polling-Make-it-eent-driven-tp3419564p3419564.html > Sent from the Karaf - User mailing list archive at Nabble.com. >
