Joern Nettingsmeier wrote:
Markus Angst wrote:
>>
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).
+1. neat idea. thorsten, iirc you came up with that feature in the first
place, right? how difficult could this be?
My Java knowledge is very limited, but I feel that tweaking
modules-core/properties/.../PropertiesModule.java would do.
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.
i don't think that's a good idea. sitemaps are about control and data
flow. i wouldn't put data itself in there.
I wouldnt call it data, it's configuration parameters. I think I would use the
feature as it was intended (also given by the example of sonfiguring a directory
name). But yes, I agree with you, that's why it's my second attempt, just to
avoid the module...
- global-sitemap.xmap is not fallback enabled (that's ok because I wouldn't
like to override it anyway)
you should not :)
I know, that's why the gods made it impossible... It only shows my impression
that the concept of the global sitemap variables could be incomplete.
fallback-overriding that one is roughly equivalent to using another CMS
altogether :)
Good to know in case of emergency ;-)
Thanks!
Markus Angst
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
