On Jan 10, 2005, at 9:07 AM, Torsten Curdt wrote:
So it seems, flow replaces components? If createNewAccount() gathers sends pages, collects information, creates an Account, etc. then why not just use cocoon.sendPageAndWait?
because this is done in the called block, not by the callee.
Yes, and when sendPageAndWait returns the calling blocks flow continues with a new account accessible from the session. Maybe we need a new method such as callFunction.
sorry, guys ...you've lost me here. I don't get the problem.
Neither do I. :-/
Problem:
flow.js of blockA
------------------
function blockAFunc() {
return helper();
}
function helper() {
return "A";
}flow.js of blockB
-----------------
function blockBFunc() {
return helper();
}
function helper() {
return "B";
}
flow.js of blockC ----------------- function blockCFunc() { print(blockB()); }
What do you expect when you call blockCFun()? A or B?
Answer: It depends on the order of declaring your scripts in <map:flow/>. The first helper() method declared will be found.
That's one of the reasons for all this noise. Otherwise I would be agree with you that we don't need isolation at this level.
-- Reinhard
