Re: Rule Engine / Dispatcher

[Deepal Jayasinghe]

Hi Paul and all;   I am sorry I was out from the list for a while , any way this is what I have in my mind regarding Synapse + Axis2     As shown in the Figure the driver is SynapseEngine , which will call AxisEngine.receive(new MC) , the looping will taken place depending on the rule status. As far as Java is concern you will some have get the java return and at that point you can decide to continue or not depending on the status properties. In this picture Synapse is not just a axis2 module.   In the following picture MessageReceiver will do the looping , at the MR it can decide depending on the status whether to continue or not , and the second approach Synapse can be deployed as an Axis2 extension module.     All the decision making logic has burn into MR in this case ,   you guys have implemented that in this way some other way I just need to clarify Thanks,  Deepal ................................................................ ~Future is Open~ ----- Original Message ----- From: Paul Fremantle To: synapse-dev@ws.apache.org Sent: Tuesday, October 18, 2005 7:20 PM Subject: Rule Engine / Dispatcher Saminda / folks I've been looking at the code you've posted. I also talked it over with Ant Elder. It seems one difference between my prototype code and yrs is that in mine the rule engine retains control. I think that it is possibly a more robust model. For example, if each rule requires a new inflow then there has to be a way for the dispatcher to maintain state. One option that occurred to us was for Synapse to launch a new AxisEngine and then retain control. Paul