Stefano Mazzocchi wrote:
> - deprecate 'internal-only' attribute of 'map:pipeline'
> [because named pipelines become implicitly internal-only]
I use something like the following:
<div class="newsbox">
<xsl:for-each select=
"document(concat('cocoon://int/news/',$pubdir))/files/file">
<xsl:sort select="@last-modified"/>
<p class="newsheadline">
<xsl:value-of select="document(@name)/document/header/title">
</p>
<p class="newsabstract">
<xsl:value-of select="substring(
document(@name)/document/header/abstract,1,42)">
</p>
</xsl:for-each>
...
and in the sitemap
<map:pipeline internal-only="yes">
<map:match pattern="int/news/*">
<map:generate type="directory" src="/my/news/{1}"/>
<map:transform src="xslt/newsfilter.xsl"/>
<map:serialize type="xml"/>
</map:match>
</map:pipeline>
Is there a better way to solve this kind of problem?
(I worked around the caching issue).
How will this be solved without internal-only pipelines?
The $pubdir is curently a parameter but there are reasons
to have it been taken from input XML in some cases. In
any case, aggregation seems not to be quite right.
Ideas, thoughts?
J.Pietschmann
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
