Hello, I have a (dare I say 'dumb'?) question regarding pipelines defined
in the sitemap. What is the difference between defining one pipeline (with
a whole bunch of match elements) and several pipelines (with the same
match elements in total, but spread across several pipeline elements). For
example, consider the following:
sitemap1 (one pipeline):
...
<map:pipelines>
<map:pipeline>
<map:match pattern="url1">
<map:generate src="docs/file1.xml"/>
<map:transform src="xsl/site.xsl"/>
<map:serialize type="html"/>
</map:match>
<map:match pattern="url2">
<map:generate src="docs/file2.xml"/>
<map:transform src="xsl/site.xsl"/>
<map:serialize type="html"/>
</map:match>
<map:match pattern="url3">
<map:generate src="docs/file3.xml"/>
<map:transform src="xsl/site.xsl"/>
<map:serialize type="html"/>
</map:match>
</map:pipeline>
</map:pipelines>
...
sitemap2 (several pipelines):
...
<map:pipelines>
<map:pipeline>
<map:match pattern="url1">
<map:generate src="docs/file1.xml"/>
<map:transform src="xsl/site.xsl"/>
<map:serialize type="html"/>
</map:match>
</map:pipeline>
<map:pipeline>
<map:match pattern="url2">
<map:generate src="docs/file2.xml"/>
<map:transform src="xsl/site.xsl"/>
<map:serialize type="html"/>
</map:match>
</map:pipeline>
<map:pipeline>
<map:match pattern="url3">
<map:generate src="docs/file3.xml"/>
<map:transform src="xsl/site.xsl"/>
<map:serialize type="html"/>
</map:match>
</map:pipeline>
</map:pipelines>
It seems to me that both forms are equivalent. So I guess my question is
'Why would one choose one form over the other?' Is it just to define
seperate "handle-errors" processing on a per pipeline basis? Thanks in
advance for your input.
Regards,
--mike
---------------------------------------------------------------------
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]>
