cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sylvain Wallez <>
Subject Re: [TreeProcessor vs Compiled] Behavior of src attribute on action-set elements
Date Wed, 06 Feb 2002 18:16:42 GMT
Peter Royal wrote:

>Given the following:
><map:action-set name="go_blah">
>	<map:act type="blah" src="1"/>
>	<map:act type="blah" src="5"/>
>and in a pipeline:
><map:act type="go_blah" src="2"/>
>In the compiled sitemap, the src parameter on the map:act in the pipeline is 
>ignored, the src defined in the action-set is used. In the TreeProcessor it 
>is the opposite, the src parameter on the pipeline map:act is used for each 
>of the actions in a set. What is the proper behavior?
>I really don't care either way, but we need to define the behavior so both 
>can do the same. I'd say having the TreeProcessor act like the sitemap would 
>be best. Just wanted to bring this up before writing a patch.
You're right : the TreeProcessor is meant to be an exact drop-in 
replacement for the compiled sitemap. But the fact that the sitemap 
specification is written in sitemap.xsl sometimes doesn't help to 
understand the details ;)

So I updated the TreeProcessor and action sets should now behave the 
same in both implementations.

>ps. TreeProcessor rocks! Development is *much* quicker, well, would be much 
>quicker if I wasn't stopping to write patches ;)
Thanks for using it :) It wasn't thoroughly tested, because the most 
complex sitemaps I have at hand are the cocoon samples, and they don't 
test everything.

I hope to have some free time next week to allow recycling of the 
TreeBuilder, which will make reload even faster ! Also, I will fix a bug 
on view-handling in map:aggregate that prevents generation of docs.


Sylvain Wallez
Anyware Technologies -

To unsubscribe, e-mail:
For additional commands, email:

View raw message