This should be done by the ErroAction, Notifying a Fault<T>when we move a message t the error queue
On Fri, Mar 20, 2009 at 8:06 PM, Mike Nichols <[email protected]>wrote: > > The problem is sending a fault message when the message is going to be > retried, right? > So it is probably better to just have a listener on the errors > subqueue and publish exceptions from there? > What things aren't recommended, Fault messages or the interception I > mentioned? > > On Mar 20, 5:00 pm, Ayende Rahien <[email protected]> wrote: > > Yes, that was raised before, and it is something that we should > > probably do.That > > said, it is generally not recommended to do such things. > > > > On Fri, Mar 20, 2009 at 7:58 PM, Mike Nichols <[email protected] > >wrote: > > > > > > > > > Apologies if this is too general of an esb question here, but I am > > > curious how folks are handling exceptions that occur on business code > > > when during a Consume(msg){}. > > > > > I was thinking of implementing something like Fault<T> that would be > > > perhaps be consumed on an OccasionalConsumer during a request/reply > > > scenario but before I go that route I wondered if I that is how others > > > are doing it. > > > > > It'd be a snap intercepting the Consumers but just feels too easy. :) > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
