<map:match pattern="view"> <map:generate src="cocoon://generate"/> <map:transform src="homePage.xsl"/> <map:serialize/> </map:match>i thought the original intention was to make the flow clearer? now we have three blocks of code to follow instead of one...
Well, almost, you can reuse your "view" pipeline:
<map:match pattern="views/*">
<map:generate src="views/{1}.xml"/>
<map:transform src="page.xsl"/>
<map:serialize/>
</map:match>The same can be done for the "call" pipeline.
is cleaner but we have many pages which need no backend data, only "simple" xsl of our standard xml stream, so we would now have to write empty javascript "flow controllers" for these pages.
In that case, don't call a flowscript. Just invoke directly a classic generator-transformer-serializer pipeline.
Ugo
