Hi,
We want to use some sort of global configuration parameters for our Lenya
publication. Right now we are only using them in sitemaps (for passing them to
XSLTs). They are not used in custom Java code yet but this is likely to happen
some day.
My first attempt was to use lenya.properties.xml. Since this works only globally
and on a module level, I have to create a module to smuggle the file into our
publication. It works, but it feels like using a big tool for a small task and I
would need a new module for every publication that needs its own
lenya.properties.xml. I think it would be a nice feature to have a
lenya.properties.xml on a publication level (just drop it into $PUB_HOME).
As a second attempt (and to avoid an extra module) I am also thinking about
using global sitemap variables (<global-variables>), which are, as I understand
it, a (almost undocumented) cocoon feature. In global-sitemap.xmap there is a
comment: "These values are inherited into sub-sitemaps and can be extended
there." This is exactly what I want but I have an understanding problem. The
following are all questions disguised as statements, so stop me when i'm going
wrong:
- inheritance goes only in the direction away from the root of the sitemap tree
- from this it follows that global sitemap variables have to be placed in
the root of the sitemap tree to be visible in all branches
- the root of the sitemap tree in Lenya is always global-sitemap.xmap
(although the filename does not appear in
http://lenya.apache.org/docs/1_4/reference/lenya-sitemaps.html)
- global-sitemap.xmap is not fallback enabled (that's ok because I wouldn't
like to override it anyway)
- from all of the above it follows that global sitemap variables cannot
be visible in all branches of the sitemap tree and survive a build except
when they are put into global-sitemap.xmap in the Lenya source tree
Again, these are all questions. Any answers, hints, pointers to documentation or
suggestions for a third approach are welcome :-)
Thanks!
Markus Angst
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
