Thank you. That works.
But: That method adds always an extra root-element to my document.
So, I would have to use the following sequence to include use only the
result of my datasource chain:
<map:match pattern="datasink1">
<map:aggregate element="mydata">
<map:part src="cocoon:/datasource"/>
</map:aggregate>
<map:transform src="remove-mydata-root-element.xsl"/>
<map:transform src="dosomething.xsl"/>
<map:serialize/>
</map:match>
That's quite ugly. I think about writing an own generator to get a slim
chain like the following one:
<map:match pattern="datasink1">
<map:generate type="get-cocoon-result" src="cocoon:/datasource"/>
<map:transform src="dosomething.xsl"/>
<map:serialize/>
</map:match>
But: I really would preferr to use an existing generator...
Cheers,
Olaf.
-----Urspr�ngliche Nachricht-----
Von: Frank Taffelt [mailto:[EMAIL PROTECTED]]
Gesendet: Mittwoch, 17. Oktober 2001 11:03
An: [EMAIL PROTECTED]
Betreff: Re: How to build a chain of xsp-pipelines?
Hi,
> <map:match pattern="datasink1">
> <map:generate src="cocoon:/datasource"/>
> <map:transform src="dosomething.xsl"/>
> <map:serialize/>
> </map:match>
you should try this way instead:
<map:match pattern="datasink1">
<map:aggregate element="mydata">
<map:part src="cocoon:/datasource"/>
</map:aggregate>
<map:transform src="dosomething.xsl"/>
<map:serialize/>
</map:match>
frank
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
