0

I'm using Rhino Service Bus and I've two sagas, SaveCustomerSaga and a ProcessReceiptSaga both of these operations send UpdateInvoicesCommand to a standard message consumer. Neither of the Sagas are completed until the Invoices have been updated. Both sagas implement Orchestrates<'InvoicesUpdated> to complete. The same CorrelationId is used for all messages.

However when the consumer of UpdateInvoicesCommand replies with the message InvoicesUpdated, it's dispatched to both Sagas! Event though one of them hasn't even been initiated and the CorrelationId belongs to the other already started Saga.

Shouldn't it dispatch it only to the appropriate Saga with the matching CorrelationId? Is there a work around or an intercept I can do to enforce this behaviour?

(Using v2.3.0, however a quick look at commit history doesn't appear to be new changes relating to this.)

Aaron
  • 579
  • 1
  • 4
  • 12
  • Hard to tell what the problem is here. If you can isolate a failing test and post to the discussion group I'll take a look. – Corey Kaylor May 15 '12 at 04:51
  • Ok so sounds like what I expect above is the way it's meant to work? And chances are I haven't configured something correctly... I have a custom Saga state persister I wrote, could it be with that? – Aaron May 16 '12 at 07:48
  • It could be, and yes it should work as you've described to the best of my knowledge. – Corey Kaylor May 17 '12 at 19:12

0 Answers0