Johnny Jones wrote:
When you say, "run it through xinclude" where is the xinclude? Is it in
the sitemaps or is it somewhere else? For example, is it in the
following files:
lenya/pubs/blog/xslt/feed/xinclude.xsl
lenya/pubs/blog/xslt/archive/xinclude.xsl
yeah, 1.2 has a clunkier way: it uses an xslt transform and then the
xlink transformer. ths xinclude xslt prepares the aggregation, and the
xlink transformer pulls it in. try it out by commenting out parts of the
pipeline. this is the ATOM feed pipeline from the blog
http://svn.apache.org/viewcvs.cgi/lenya/branches/BRANCH_1_2_X/src/webapp/lenya/pubs/blog/sitemap.xmap?rev=170255&view=markup
<map:match pattern="*/feeds/*/index.xml">
<map:act type="resource-exists">
<map:parameter name="url" value="content/{1}/entries"/>
<map:generate type="directory" src="content/{../1}/entries">
<map:parameter name="depth" value="4"/>
<map:parameter name="reverse" value="true"/>
</map:generate>
<map:transform src="xslt/feed/xinclude.xsl">
<map:parameter name="feedid" value="{../2}"/>
</map:transform>
<map:transform type="xlink">
<map:parameter name="href" value="content/{../1}/dummy.xml"/>
</map:transform>
<map:serialize type="xml"/>
</map:act>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
