Sorry, I got totally lost in all these mails. As far as I understand we
are currently discussing when/where it's possible to set the running mode.
There are two places: applicationContext.xml and system property. The
system property takes precedence over the applicationContext.xml. I'm
not sure which role cocoon.xconf should play in this?
Carsten
Giacomo Pati wrote:
>
>
> Leszek Gawron wrote:
>>> Felix Knecht wrote:
>>>> + final String runningMode =
>>>> getSystemProperty(Settings.PROPERTY_RUNNING_MODE,
>>>> this.getAttributeValue(element, RUNNING_MODE_ATTR, null) );
>>> 1. the logic for obtaining running mode is scattered again
>
> You seem to have a problem with that :-)
>
> No, seriously. It seems a little over engineered at first as I cannot
> imagine anyone willing to have its own implementation of a
> getSystemProperty method (beacause they are protected). On the other
> hand (if we make those method private) I find the solution from Felix
> quite simple.
>
>>> 2. system property takes preference over the setting in cocoon.xconf. Is
>>> that correct?
>
> Yes, I think the System property should take precedence over the setting
> in cocoon.xconf
>
> --
> Giacomo Pati
> Otego AG, Switzerland - http://www.otego.com
> Orixo, the XML business alliance - http://www.orixo.com
>
--
Carsten Ziegeler - Chief Architect
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
|