cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <>
Subject [RT]: Unifying input modules and global parameters
Date Thu, 27 Jun 2002 11:39:07 GMT
In the latest CVS of 2.1, I think we have two overlapping 
concepts: the global parameters and the input modules.
Perhaps we could merge the global parameters somehow into
the input modules and then remove the global parameters
as a separate concept again.

Current State

Currently, the global parameters are declared in the
map:pipelines section of a sitemap and the scope
is the map:pipeline sections.
So, if you want to refer to a global parameter, for
example named "skin", you have to use
{skin}, or {../skin} etc. depending on the depth of
your statement in the map:pipeline section.

- If you refer to a global parameter, you have to
  precisly specify the path (= count the ../)
- global parameters are not inherited/available to 

- Configuration directly in the sitemap

The input modules are completly defined in the cocoon.xconf,
they can be used inside every sitemap by first choosing
the input module and then the key, like {request:parametername}.

- Simple use
- Single configured values are available in all sitemaps

- Configuration is not in the sitemap, but in the cocoon.xconf

Proposed Solution
Make one input module sitemap configurable, like the 
authentication manager. This means a (global) input module is
defined in the cocoon.xconf, but can be additionally configured
in the sitemap.
A subsitemap inherits this configuration from it's parent sitemap
and can add own key/value pairs, so this would look like this:


So, the key {global:skin} is available in this sitemap and in
all sub-sitemaps.

Comments? Suggestions?


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

View raw message