[EMAIL PROTECTED] wrote:
Thats right - I would like to aggregate menu content with CForm content and style them into
a single page.
Franco
Ok, I have an example of that in my work. Code can be seen bellow.
My third match triggers the flow script, from which the CForm is
initialised. In the flowscript I do 'call-display-pipeline' to display
my form. As you can see, that gets caught by the second match which
aggregates my page together (header footer & everything in between), the
second match aggregates the 'CFORM' produced by the call to the first
match "display-pipeline" (by doing <map:part src="cocoon:/{1}-{2}">)
1. <map:match pattern="display-pipeline">
<map:generate type="jx" src="cforms/newsletter_template.xml"/>
<map:transform src="xslt/form/forms-samples-styling.xsl">
<map:parameter name="root"
value="/cms/{page-envelope:publication-id}/live"/>
</map:transform>
<map:serialize/>
</map:match>
2. <map:match pattern="call-*-*">
<map:aggregate element="cmsbody">
<map:part src="xml/dynamicpage_head.xml"/>
<map:part src="xml/top_nav.xml"/>
<map:part
src="cocoon://navigation/{page-envelope:publication-id}/live/tabs/index.xml"/>
<map:part src="cocoon:/{1}-{2}">
<map:generate src="flow-attr:body" />
<map:serialize type="xml" />
</map:part>
<map:part
src="content/{page-envelope:area}/footer/index_en.xml"/>
<map:part src="xml/footerlinks.xml"/>
</map:aggregate>
<map:call resource="page-xhtml"/>
<map:call resource="finish"/>
</map:match>
3. <map:match type="usecase" pattern="newsrequest">
<map:call function="newsRequest"/>
</map:match>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
