cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicola Ken Barozzi" <>
Subject Re: [RT] InputModules for sitemap variables
Date Mon, 27 May 2002 08:58:12 GMT
From: "Christian Haul" <>

> On 26.May.2002 -- 01:50 PM, Sylvain Wallez wrote:
> > Nicola Ken Barozzi wrote:
> > >From: "Sylvain Wallez" <>
> > >>So the following snippet (copied from RequestParamAction javadoc) :
> > >> <map:act type="request">
> > >>   <map:parameter name="parameters" value="true"/>
> > >>   <map:generate src="users/menu-{id}.xml">
> > >> </map:act>
> > >>
> > >>could be written more simply :
> > >> <map:generate src="users/menu-{request-param:id}.xml"/>
> > >>
> > >
> > >It doesn't bring new functionality, creates duplicate ways of doing the
> > >*same* thing, and breaks compatibility with old sitemap.
> > >All this in favor of a more compact syntax.
> > >
> >
> > Wow, this is harsh !

Sorry, it was not intended that way :-/

> > My opinion is that it brings more *usability* in the sitemap, since
> > there is currently no *simple* way to substitute anything else than
> > sitemap variables. This led to what I consider to be a degenerate use of
> > matchers and actions to populate these variables.
> I'd like to second you on that.

After Sylvain's second mail, I'm starting to agree too.
If URLs have sources, why don't sitemap parameters have them?

> > Concerning compatibility, the colon separator is just a proposal, and we
> > have to see if anybody already uses it. If some people do, there are
> > other possible syntaxes, such as "attaching" module substitution to the
> > root of the variable tree, i.e. "menu-{/request-param:id}.xml". Since
> > '/' is currently used to travel up the hierarchy, I'm pretty sure nobody
> > uses it as the first character of variable names.
> I like this idea of using the root space for this. OTOH after a bit
> consideration I'd be happy without "/" as well.

It seems that sitemap parameters need to be defined in a more specified
manner, as urls are.

Currently there is a ../../..etc mechanism, but not a real formal
specification-contract as for urls AFAIK.

My previous remarks on using modules only for Actions-Matchers and Selectors
were wrong, as I found out myself thinking over the proposals. It implied
that pipeline components operate on uris while Selectors, Matchers and
Actions operate on sitemap parameters, which is plain wrong.
All of these components get input from somewhere, which is not really

How about using URIs and URLs as the *only* way of describing locations?

This means that sitemap variables would be defined as URIs-URLs, and Modules
ans Sources would simple be ways of getting data from a data source.

Given this, I'm +1 for the proposal.

Nicola Ken Barozzi         
            - verba volant, scripta manent -
   (discussions get forgotten, just code remains)

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

View raw message