Hi all, I'm reading through all the documentation of Camel. I'm really excited but due to the extent of the docs and my lack of experience on it, I'd appreciate if somebody give some guidelines on the following scenario. I want to keep things as simple as possible :)
- I have to have a decoupled server running Camel; - systems will access the Camel server through Webservices - I cannot have Camel clients or use RMI; - I think on creating webservices to handle the demand as in the camel-example-servlet-tomcat - have routes that based on the servlet "from" will schedule a calendar Job on Quartz (these are dynamic jobs - which are scheduled and unscheduled several times, per client - we need to pass specific JobDataMap as well) - Quartz will trigger a JMS call when its time - systems will consume the messages and start the jobs Any thoughts and guidance where should I focus on my learning ? How can I chain the message from servlet -> quartz -> activemq ? (any samples) tks PS. We could do this without Camel of course. But Quartz is only the tip of the iceberg and our first integration... -- View this message in context: http://camel.465427.n5.nabble.com/Newbie-question-Topology-for-Camel-Servlet-Quartz-JMS-tp5665134p5665134.html Sent from the Camel - Users mailing list archive at Nabble.com.
