"mark.little(a)jboss.com" wrote : "ddunkin" wrote : I have a ProcessPurchaseOrder document that comes into the system. That document is routed to the order management system for the supplier identified in the document. Now what I want to do is send a copy of all ProcessPurchaseOrder documents to a component that will extract certain information and store it for statistical analysis. It's a separation of concerns. The listener doesn't need to know anything about the statistical analysis. Neither does the order management system. | | | | So this is routing sequentially though? I had assumed you were maybe talking about routing the message concurrently, e.g., like a broadcast of the message to multiple destinations. | No, it would be concurrent. The order management system shouldn't have to wait for the statisticl analysis system. "mark.little(a)jboss.com" wrote : | anonymous wrote : | | Another example is a document that contains hours worked on a case where the employee working the case is paid billable time. That document should go to both receivables, so that the client can be billed, and to payroll, so the employee can be paid. | | Is this done sequentially or concurrently? Do you wait for the receivables to ack before sending to the payroll? If the answer is yes, then there's not really a problem AFAICT. If the answer is no, then we're talking about "asynchronous" interactions and, assuming the sender wants some kind of ack from each, the underlying infrastructure will need to be able to tally responses with "rendezvous" requests from the client, in just the same way it would for any "asynchronous" interaction. It would be concurrent. I think the assumption that the sender needs an ack from each receiver is not necessarily true. In fact, the sender doesn't even need to know where the message is going, just that the message was received by the ESB. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980787#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...