Joerg Heinicke wrote:
On 17.12.2007 1:31 Uhr, Kamal Bhatt wrote:
Can you move your variable into the parameters of a new pipeline?
<map:match pattern="test-xsp-action">
<map:act type="xsp-action" src="my-xsp-action.xsp">
<map:generate
src="cocoon:/parsexspaction/{my-xsp-action-variable}"/>
<map:serialize type="xml"/>
</map:act>
</map:match>
<map:match pattern="parsexspaction/**">
<map:generate type="file" src="test2.xml"/>
<map:transform src="{1}/myxslt.xslt"/>
<map:serialize type="xml"/>
</map:match>
How can I aggregate this though?
His solution is indeed a nice work around, similar to passing an
additional method parameter:
<map:match pattern="test-xsp-action2">
<map:act type="xsp-action" src="my-xsp-action.xsp">
<map:aggregate element="test1">
<map:part src="cocoon:/test-xsp-action/{my-xsp-action-variable}"/>
<map:part src="{testXML}"/>
</map:aggregate>
</map:act>
<map:serialize type="xml"/>
</map:match>
<map:match pattern="test-xsp-action/*">
<map:generate type="file" src="test2.xml"/>
<map:transform src="{1}/myxslt.xslt"/>
<map:serialize type="xml"/>
</map:match>
OK, thanks, that makes more sense to me. Not exactly what I want, but I
could make it work.
Thanks.
--
Kamal Bhatt
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
