It seems like a lot of noise to avoid a log statement. On Thu, Mar 10, 2011 at 1:23 PM, Mike Nichols <[email protected]>wrote:
> When you implement your own way of finding the saga you could also provide > a persister that can handle the TIme based on the message type or other > convention. > Similarly I would think you could apply the same convention based on the > message to return a NoOp saga in the case where the saga has timed out. > You could probably do this at the ISagaPersister implementation level too I > suppose but it is simple to override the saga discovery and have total > control. > > > On Thu, Mar 10, 2011 at 1:06 PM, Jason Meckley <[email protected]>wrote: > >> Mike, how would this be different than the default message finder? I still >> have the issue where the saga was completed, but the timer elapsed, thus >> returning a null saga and getting the "no consumers" log error. >> >> -- >> 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. >> > > -- > 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. > -- 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.
