If they are processed in the order they are declared than what I want to
achieve will work.
You can have a match inside a match with parameters. The first match is used
for the URL pattern, the second match is for the id parameter that is added
to the end of the URL. I should have had TSS-ProjectNameHere{1}.html in
<map:generate ... />
So if the URL pattern is
http://commerce.wu.gov/tss/TSS-SomeProject.section?id=paramvalue
The first match processes TSS-SomeProject.section to find the file named
TSS-SomeProject.html and the second match gets the value for the id
parameter (paramvalue) and passes that as a parameter to the xslt process.
-----Original Message-----
From: Ben Pope [mailto:[EMAIL PROTECTED]
Sent: Friday, April 29, 2005 1:53 PM
To: users@cocoon.apache.org
Subject: Re: sitemap processing
Schultz, Gary - COMM wrote:
> I just want to confirm or clarify my understanding of the sitemap process.
> Does the Cocoon pipeline process the includes first and the xslt second? I
They are processed in the order they are declared. I'm not sure the
following makes sense:
> plan to use a sitemap entry as shown below in a project management system:
>
> <map:match pattern="TSS-ProjectNameHere*.section">
> <map:generate src="d:/comwps/TSS/content/TSS-ProjectNameHere.html"/>
> <map:match type="match-param-paramname" pattern="*">
> <map:transform type="xinclude"/>
> <map:transform type="cinclude"/>
> <map:transform src="d:/comwps/TSS/xslt/page2html-docplan.xsl">
> <map:parameter name="id" value="{1}"/>
> </map:transform>
> <map:serialize/>
> </map:match>
> </map:match>
Having a match inside of a match is wrong.
And starting a match without a generator is also wrong.
What are you trying to achieve?
The idea is that you match something, then:
Generate (arbitrary data to SAX events)
Transform (SAX events to SAX events)
Serialise (SAX events to arbitrary data)
You can transform 0 or more times. The output of one component feeds
into the input of the next.
Ben
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
