cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Donald Ball <ba...@webslingerZ.com>
Subject Re: Small note on sitemap configuration
Date Thu, 01 Jun 2000 03:47:30 GMT
On Thu, 1 Jun 2000, Giacomo Pati wrote:

> > Go back to my language example:
> > 
> > <process uri="/foo/**">
> >  <choose>
> >   <when test="language">
> >    <generator type="parser" src="./foo/{language}/**"/>
> >   </when>
> >   <otherwise>
> >    <generator type="parser" src="./foo/en/**"/>
> >   </otherwise>
> >  </choose>
> >  ...
> > </process>
> > 
> > How would you propose to rewrite this example using your matcher elements?
> > 
> > > -1 on the use of XPath as testing logic (for the problems outlined
> > > above).
> > >
> > > You might want to look into the "Pipeline Conditional Model" thread and
> > > comment on what I proposed there.
> > 
> > I don't see anything in that proposal about accessing the value of
> > request-time variables in the configuration of the resolver components -
> > which I think is key. I don't see any problems with XPath expressions that
> > don't apply equally well to anything else that accomplishes the same goal.
> > Maybe I have missed something though?
> 
> Just a quick thought about this. What if we have a
> "SitemapPropertyManager" class (I don't want to call it a Component)
> that is responsable for resolving {variable}? A default version could
> implement request information. If someone has special needs he could
> subclass, extend or make his own to have such properties available.

Mime
View raw message