Just to clarify: what I added was the "cocoon.parameters" property that contains a map of the parameters passed from the sitemap. The parameters are also passed positionally to the function as before. So if you want to access a named parameter you can do this:
<map:call function="myFlow">
<map:parameter name="x" value = y"/>
...
function myFlow() { var x = cocoon.parameters.x; }
The same functionality is in the original flow implementation.
Do we want something different?
That is perfectly ok. Also, would "cocoon.parameters" make sense for <map:call continuation> also ? IMO yes, as otherwise there's no means to pass e.g. parts of the URI (matcher wildcards) to the continued script.
What do you think ?
Sylvain
-- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects } Orixo, the opensource XML business alliance - http://www.orixo.com
