Hi Venkat, Please find answers inline below.
On Tue, May 24, 2016 at 9:29 PM, Venkat Raman <[email protected]> wrote: > > > 1) Why are we pushing variables in carbon message variables stack..?? > One of the features of the language is to have variables we can declare and use throughout the mediation flow. We are able to populate variables during loading and during runtime and so variable stack is kept inside the carbon message so each thread has its own variable stack. Hope that clarifies. > 2) Also could you kindly explain how AbstractFlowController and > FlowControllerCallback are working together. My understanding is not quite > clear on this. > AbstractFlowControllers are mediators that require controlling the flow (like filter mediator) where we the mediation flow branching out, in which case we want to mediate only the branch we're in and FlowControllerCallback is a CarbonCallback that we pass on to receive method of mediators of a particular branch. This allows us to continue mediation from the parent once a branch is complete. You can test this out by debugging the FilterMediator, try passing on the usual callback and then check by passing on a FlowControllerCallback. @IsuruR, please correct me if I'm wrong. :) Thanks, -- *Ravi Undupitiya* Senior Software Engineer; WSO2 http://wso2.com *E-mail: [email protected] <http://wso2.com>**M: **+94 772 930 712 <%2B94%C2%A0772%20930%20712>* Lean . Enterprise . Middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
