... but even if this is the solution, what about off-the-shelf participants? For example, I'm getting errors when trying to cancel a process that uses the built-in MailParticipant. What can I do to ensure that this participant can handle the CancelItem (other than wrapping it inside a custom participant)?
On Sep 17, 2:42 pm, Matt Zukowski <[EMAIL PROTECTED]> wrote: > So basically what you're saying is that at the top of a participant's > implementation I should have something like: > > return if workitem.kind_of? OpenWFE::CancelItem > > (Assuming that I don't need to take any special actions to handle the > cancellation) > > Or am I getting this all wrong? > > On Aug 29, 7:21 pm, "John Mettraux" <[EMAIL PROTECTED]> wrote: > > > On 8/30/07, John Mettraux <[EMAIL PROTECTED]> wrote: > > > > For now, I will simply discard cancelitems for BlockParticipant to > > > avoid any such trouble. OK for you ? > > >http://rubyforge.org/tracker/index.php?func=detail&aid=13507&group_id... > > > Maybe we should keep track of blocks and cancel them altogether... > > > Hi, > > > I won't touch at the BlockParticipant implementation, it's up to the > > BlockParticipant to handle properly incoming CancelItem instances, the > > engine can't and shouldn't care, the participant knows what's going > > on, not the engine. > > > Best regards, > > > -- > > John Mettraux -///- http://jmettraux.openwfe.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenWFEru 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/openwferu-dev?hl=en -~----------~----~----~----~------~----~------~--~---
