We have a requirement to implement a polling consumer that periodically checks for messages (via Web Service or RMI requests). In this case the polling consumer expects to invoke multiple requests until all messages have been read without waiting for the next polling (there is a ‘No More Messages’ flag in the result of each request). The messages further processing is expected to be done by multiple threads. I am new to Camel (we looked at it a long time ago but never had a chance to use it). I couldn’t find an obvious way to achieve the above, a loop processor could help but we don’t process the same message multiple times and in this case it is not a ‘for’ loop with a counter. I also considered ‘splitter’ but in this case we will have to read all available messages first before continue processing and we prefer to send each message immediately after getting it to a pool of multi-threaded executors. We will most likely define the endpoints using Spring beans and implementation will be using Java DSL. Any suggestions on how to achieve the above will be great.
-- View this message in context: http://camel.465427.n5.nabble.com/Polling-Consumer-invoking-multiple-requests-tp5599204p5599204.html Sent from the Camel - Users mailing list archive at Nabble.com.
