Hello,
I posted this on stackoverflow as well...
http://stackoverflow.com/questions/2916213/rhine-servicebus-sagas-with-multiple-messages
I have a saga that can handle multiple messages like so:
public class OrderSaga : ISaga<Order>
, InitiatedBy<StartOrderSaga>
, Orchestrates<CancelOrder>
, Orchestrates<PaymentForOrderReceived>
, Orchestrates<CheckOrderWasPaid>
, Orchestrates<OrderAbandoned>
, Orchestrates<CheckOrderHasBeenShipped>
, Orchestrates<OrderShipped>
, Orchestrates<CheckOrderHasDelayDuringShipment>
, Orchestrates<OrderArrivedAtDestination>
, Orchestrates<OrderCompleted>
{...}
but only Orchestrates<CancelOrder>, the first, seems to be picked up. So I
suppose (I did not find the line, but am under a strong impression this is
so), that only the first Orchestrates is registered.
Probably this is by design. From what I imagined a saga to be, it seems only
logical that it receives many different messages, but I might be wrong. I
might be wrong with my whole assumption, too :)
How am I supposed to handle this? Are Sagas supposed to only handle one (in
my case) a ChangeStateMessage or should I wire the other
ConsumerOfs/Orchestrates by hand?
--
Jan
--
You received this message because you are subscribed to the Google Groups
"Rhino Tools Dev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/rhino-tools-dev?hl=en.
