Sitemap element order relevant?

[Jeff Turner <je...@apache.org>]

Hi,

In the Forrest sitemap, 40% of the space is taken up by components, views
and resources, which aren't particularly interesting to a new user.  I'd
like to have <map:pipelines> right at the top.  This works, and validates
against the RNG grammar.  If anyone knows of a reason why this
_shouldn't_ be done, please let me know :)

thanks,

--Jeff

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

Re: Sitemap element order relevant?

[Alexandre Victoor <al...@fr.adp.com>]

Hi
I don't know if you can declare pipelines before components... perhaps it 
would be cleaner to mount a second sitemap where you would write your 
pipelines.
In sitemap.xmap you would write something as follows :

<map:pipeline>
         <map:match pattern="your pattern">
                 <map:mount uri-prefix="" check-reload="yes" 
src="your_pipeline_sitemap.xmap"/>
             </map:match>
  </map:pipeline>

Look at the sitemaps of the cocoon samples for more examples of sitemap 
mounting.
Hope it helps.

Alex



At 15:19 06/07/2003 +1000, you wrote:
>Hi,
>
>In the Forrest sitemap, 40% of the space is taken up by components, views
>and resources, which aren't particularly interesting to a new user.  I'd
>like to have <map:pipelines> right at the top.  This works, and validates
>against the RNG grammar.  If anyone knows of a reason why this
>_shouldn't_ be done, please let me know :)
>
>thanks,
>
>--Jeff
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>For additional commands, e-mail: users-help@cocoon.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org