On 10.Jul.2001 -- 11:23 AM, Berin Loritsch wrote:
> For example, If I have a general pipeline declaration that
> works like this:
>
> <map:generate src="docs/{1}.xml"/>
> <map:transform src="stylesheets/1.xsl"/>
> <map:transform src="stylesheets/2.xsl"/>
> <map:transform src="stylesheets/3.xsl"/>
> <map:serialize>
>
> Then I would have to add another entry like this:
>
> <map:generate type="serverpages" src="docs/{1}.xml"/>
> <map:transform src="stylesheets/1.xsl"/>
> <map:transform src="stylesheets/2.xsl"/>
> <map:transform src="stylesheets/3.xsl"/>
> <map:serialize>
>
Berin, you could use resources to make this a little less cumbersome:
<map:resource name="1-2-3">
<map:transform src="stylesheets/1.xsl"/>
<map:transform src="stylesheets/2.xsl"/>
<map:transform src="stylesheets/3.xsl"/>
<map:serialize>
</map:resource/>
<map:generate src="docs/{1}.xml"/>
<redirect-to resource="1-2-3"/>
<map:generate type="serverpages" src="docs/{1}.xml"/>
<redirect-to resource="1-2-3"/>
Or -- like you said -- another matcher / selector within your
pipeline.
> Thoughts, Comments?
I like the idea because I think it's a very common use
case. Especially if it doesn't cost much or is almost free to get.
Chris.
--
C h r i s t i a n H a u l
[EMAIL PROTECTED]
fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
