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.
Btw: while working on the javaflow stuff I felt a very strong urge to refactor the sitemap-flow interface.
(see the JavaInterpreter in the javaflow block. I've put a revisit into the callFunction method)
cheers -- Torsten
