(configurator) =>
{
configurator.Correlate(this.SomeEvent, (saga, message) => (saga.Id1 == message.Id1 && saga.Id2 == message.Id2);
}
--
You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to masstransit-dis...@googlegroups.com.
To post to this group, send email to masstrans...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/masstransit-discuss/0ff90160-bfd5-404e-befc-b45cf02c8392%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
That is exactly how it should work, glad it actually does :)
On Tue, Jul 7, 2015 at 2:23 PM, <robinb...@gmail.com> wrote:
Hi all,I'm using MT2 with Automatonymous. I have a state machine that correlates messages using the StateMachineSagaRepositoryConfigurator callback.
(configurator) =>
{
configurator.Correlate(this.SomeEvent, (saga, message) => (saga.Id1 == message.Id1 && saga.Id2 == message.Id2);
}My question is what is the expected behavior if the correlation step matches multiple saga instances? Doing some quick tests, it seems like if an event correlates to multiple instances, the event is raised on each instance. This is actually the desired behavior I was looking for, but I wanted to check to see If perhaps I was misunderstanding how it should work. Thank You.- RBJ
--
You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to masstransit-discuss+unsub...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to masstransit-dis...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/masstransit-discuss/94e2fd5c-5aab-4659-8809-b089fa40845b%40googlegroups.com.