Generating graphics

At the end of the pipeline, different Serializers can generate different output formats, provided they're fed the right data (i.e. the required XML elements and namespaces).

Let's generate a simple graph out of of our request parameters. If your have an SVG plugin in your browser you can view the result: red/request.svg or blue/request.svg. If you don't have an SVG plugin see below for the bitmapped version of the same image.

Sitemap excerpt

<map:match id="svgRequest" pattern="*/request.svg">

<map:generate type="request"/>

<map:transform src="xsl/request-to-svg.xsl">

<map:parameter name="fillColor" value="{1}"/>

</map:transform>

<map:serialize type="svgxml"/>

</map:match>

XSL transformation

<xsl:template name="main" match="/">

<defs>

</filter>

</filter>

</defs>

<xsl:value-of select="concat('color:',$fillColor)"/>

</text>

<xsl:apply-templates select="//h:header[position() < 5]"/>

</g>

</svg>

</xsl:template>

Typical output

<defs>

</filter>

</filter>

</defs>

<text y="80" x="65" style="fill:#FFFFFF;font-size:24;font-family:TrebuchetMS-Bold;filter:url(#blur2);"> color:red </text>

</g>

</svg>

Bitmapped output

Post-processing the SVG output allows us to generate JPEG (cyan/request.jpeg) or PNG (black/request.png) images, simply by configuring a different serializer at the end of the pipeline.

Sitemap excerpts

Note the use of the cocoon:/ protocol to re-use the previous pipeline as input: when a request to blue/request.png is received, the output of the blue/request.svg is used as the input of the first pipeline shown below.