Hi there. I ran across another issue in my continuing quest to convert an app from NSB to RSB. NSB provides the concept of saga finders (IFindSagas). Saga finders allow us to pull up sagas when a message is received, even if the message is not an ISagaMessage. These are particularly useful when a saga needs to send a message to another service that will send a return message that causes the saga to "spin up" again. These return messages do not implement ISagaMessage, as the other process is completely isolated and unaware that the messages are used in sagas.
As far as I can tell, in order to "spin up" an active saga in RSB, a message MUST implement ISagaMessage. My question is, then, how do you pull up an existing saga if you don't have an ISagaMessage, but you DO have a way of fetching the SagaId? Here is a simple example: There is an isolated service, the FraudCheckService, that receives RunFraudCheck messages and replies with RunFraudCheckComplete messages. There is another service that has a saga that involves checking for fraud. The RunFraudCheckComplete message does not implement ISagaMessage, but with NSB's IFindSagas<> interface I can find active sagas based on some other criteria. I don't want to force the RunFraudCheck and RunFraudCheckComplete messages to be ISagaMessages, as they should not be aware they are being called from within sagas. Does this make sense? Is there any way I can do this? Is there another way to handle it? Thank you, tyler burd --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
