On 10/20/05, Vikas <[EMAIL PROTECTED]> wrote:
Defaults.
Ok,i got it.Then, RuleEngine needs to populate again, and it can be run in the same thread and this can be done simply by setting a property in the input MessageContext. So MessageReciever has to be properly designed
hi!What i meant here is that the mediation has three options:true => Continue
false=>Stop processing this message
Defaults.
false+new message=>stop processing this message, start working on the new message as if its anew request from outside.
Ok,i got it.Then, RuleEngine needs to populate again, and it can be run in the same thread and this can be done simply by setting a property in the input MessageContext. So MessageReciever has to be properly designed
Sorry for any confusios that i would have caused.. Was only hinting towards the possible scenatios..[oops: forgot the idea of the fault that it can generate, but can keep it out of consideration :-)]Thanks!----- Original Message -----From: Saminda AbeyruwanSent: Thursday, October 20, 2005 5:57 PMSubject: Re: Rule Engine / Dispatcher1) What i was hinting at it that the engine can't be remembering the actual message it had passed on to the Mediation. So a mediation will have to tell the engine that it had not changed something and the engine can still pursue the branch - The mediation returns a true.2)In case the mediation does change something, it returns a false and injects a new message into the system. [notice the bold text above] I used the term 'as if' because it is not actually a new message, its just a modified request re-introduced by the mediation.This is rather confusing to me. Please enlightened us.
There should be a way to Syanpse to "stop" processing the current message and let it go to the bus. How would it be able to do it, if "false" means "end of processing" instead anything else.
