I have a use-case of a message-driven bean intercepting a JMS message, then triggering a Camel route inside another class. I currently have it sending the message to the createRoute method, which then uses a producertemplate to start the context, place the message on the first endpoint queue, then the route picks it up and runs.
I could also have the MDB put the message on the first endpoint queue, then start the route, but it seems like things could get out of sync there unless I am using dynamic queue names, etc. to keep threads apart/from overlapping. Also thought of a timer route object that just constantly runs the camel route, which just keeps checking that first endpoint queue, and if a message exists, run with it, but then that timer route would have to be kicked off at some point right after server startup, and then would eat up a thread just doing scheduler-type work. Any cleaner ideas here? -- View this message in context: http://camel.465427.n5.nabble.com/Automatic-Camel-route-triggering-with-Java-DSL-tp5754696.html Sent from the Camel - Users mailing list archive at Nabble.com.
