> AFAIK it's generally not recommended to use the document()
> function in Cocoon, but rather aggregation
Andreas, you're absolutely right, which is why I used the
cocoon:/ internal pipeline and passed the URI in as an
XSLT parameter.
Sitemap:
<map:pipeline internal-only="true">
<map:match pattern="pipeline2">
<map:generate type="faultreader" />
<map:serialize type="xml" />
</map:match>
</map:pipeline>
<map:pipeline>
<map:match pattern="pipeline1">
<map:generate src="mysvg.svg" />
<map:transform type="xslt" src="merge.xslt">
<map:parameter name="dataUri"
value="cocoon:/pipeline2" />
</map:tranform>
<map:serialize type="svg2png" /> <!-- from top of
head -->
</map:match>
</map:pipeline>
XSLT:
<xsl:stylesheet xmlns:xsl="..." xmlns:svg="...">
<xsl:param name="dataUri" />
<xsl:variable name="document($dataUri)/topnode" />
<xsl:template /> <!-- input->output copying code -->
<xsl:template match="svg:[EMAIL PROTECTED]'12345']/@style">
<!-- This template matches the style attribute on a
a selected group -->
</xsl:template>
</xsl:stylesheet>
I assert that this technique is tremendously powerful, and works with
Cocoon, not against it.
Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
