Hi,
Alexander Klimetschek schrieb:
> On Thu, Dec 10, 2009 at 11:13, Felix Meschberger <fmesc...@gmail.com> wrote:
>> (O2) Add support for RunModes
>>
>> Our CMS system leverages the RunMode service from
>> contrib/extensions/runmode to detect whether the system is running as an
>> authoring or a publishing instance.
>>
>> So, we could enhance the entries in the /etc/map structure to optionally
>> provide a sling:runmode property (single- or multi-value string type).
>> If such a property is set, the entry is only used if the
>> RunMode.isActive(String[]) returns true.
>
> I could also think of a structure with a subfolder per runmode, as it
> is done by jcrinstall for install and config folders. Eg.
>
> /etc/map
> + runmode1
> +http
> + server.com
> ....
> + runmode2
> +http
> + server2.com
> ....
>
> Might be clearer. It doesn't allow for mapping a mapping config node
> to multiple folders, but one could easily copy the config to multiple
> locations.
>
> If the runmode bundle is considered optional, this could also be an
> optional feature, ie. if no runmode bundle is present, the differences
> are ignored and all configs are applied. The question is if that is
> breaking backwards-compatibility in some way? I think if the runmode
> folders are marked, eg. by a special node type, one could easily
> separate between a config with runmode folders "in between" or a plain
> existing one.
I don't like this option, because it creates issues:
* copy-paste is always problematic (yes, my option O1 has then
same issues)
* merging two tree structures creates additional issues with
respect to ordering and expected behaviour (rember that a
system may be running with more than one run-mode, so this
merge is required)
* Other than merging this is more or less the same as my
option O1 (ok, that's not really a reason for dislike but ;-) )
Regards
Felix
