Sylvain Wallez wrote:
>
> [EMAIL PROTECTED] wrote:
>
> >>I think, the proposed {\1} looks nice. And its very easy to understand.
> >>
> >>
> >
> >Other comments?
> >
>
> We don't support absolute paths for now, although it can easily be added
> in o.a.c.treeprocessor.variables.PreparedVariableResolver.
>
> We also have the (hidden ?) <map:global-parameters> feature which
> defines the first level or sitemap variables. These are the ones that
> should be accessed by the /-rooted notation.
>
> <map:pipelines>
> <map:global-parameters>
> <map:parameter name="img-dir" value="foo"/>
> </map:global-parameters>
>
> <map:pipeline>
> <map:match src="*.gif">
> <map:read src="{/img-dir}/{1}.gif"/>
> </map:match>
> </map:pipeline>
> </map:pipelines>
>
> Naming note : what about renaming "global-parameters" to
> "global-variables" ? Parameters are built by the sitemap for use used by
> components, whereas variables are set by components and given back to
> the sitemap for {} subsitution. So the "global-variables" names seems to
> me more appropriate.
>
> How does it sound ?
>
Ehm, since approx. two hours we don't have "global-parameters" anymore!
Yuppi!
Serious: we had this discussion several months ago to unify the
"global-parameters" with the input modules and I exactly did this:
We have a new input module "global" which can be configured in the
sitemap like the authentication handlers. The name for this
configuration is ...tata...global-variables.
Carsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
