Gianugo Rabellino wrote:
The problem with cocoon.xconf is that it is part of the war file.
This
makes it very difficult for our operations folks to change it since it
will get over-ridden each time the app is redeployed.
Doesn't have to be. The location of the .xconf is specified in web.xml
(now, if you ask me, it could well be a system property). This is how
exactly how we handle different configurations: they are stored
elsewhere (actually version-controlled inside the project itself) and
referenced by the web.xml setting. Same for logkit.xconf.
Ciao,
I think you missed the point. 99% of cocoon.xconf belongs in the war
file, hidden away. However, there are a few configuration items such as
the pool sizes that need to be configured when Cocoon is started, not
when the war is built. IMO, that is the value of Carsten's enhancement.
Ralph
