Hi Claus ! Thank you for welcoming me in the Camel community. I'm honored that you replied to my question .
Yet, I'm afraid it's not that simple : as I wrote it earlier, I played with the Aggregator and I guess it's almost what I'm looking for. I came to that pattern thanks to your book and the other reference book about EIP. What I have doubts about is the completion criteria. The case I described was voluntarily simplified but my patterns are much more complex. For instance, I have a process that should be able to receive an undetermined number of messages (let's say of type "Item") and when a single message "EndOfOrder" is received, then the process sends another message on the message broker saying the order has been completed. And that message triggers another process and so on. About the correlation, I had exactly the same "problem" with BPEL process manager : my messages have no correlation between them : they come from different routes linked to different partners who have nothing in common. I was forced to trick the system by asking all the partners to enter a fake property on which I could base my correlation. It's working but I'm not fully satisfied with it ... What I'm looking for, is exactly the Oracle | BEA WLI message broker feature : channels with components listening for some messages, matching the criteria I've defined, that's all. No correlation needed. First, my team and I wanted to implement that solution using topics & MDBs, aiming at full stateless solution (to meet our scalability requirements) but we thought it would be reinventing the wheel. So we naturally thought of Camel, but from what I read it does not propose the exact solution (which is pretty normal I guess), but I hope we can build it around Camel though. As you designed the Aggregator pattern, you're my best shot to understand whether it will fit my need or not. Thank you for your patience and your time. Best regards, Maxence. -- View this message in context: http://camel.465427.n5.nabble.com/EIP-Can-you-please-help-me-choose-a-correct-design-pattern-tp3412244p3413734.html Sent from the Camel - Users mailing list archive at Nabble.com.
