cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reinhard Pötz <>
Subject Re: Spring Configurator - filter/include strategy
Date Tue, 15 Jul 2008 14:41:25 GMT
Carsten Ziegeler wrote:
> Grzegorz Kossakowski wrote
>> Yes, agreed but still I cannot help my feeling that such conditionals 
>> are simply a bad idea. Having everything in one place is a benefit of 
>> course but on the other hand I would prefer to use directories or file 
>> name patterns (known from file systems) to distinguish between 
>> various, separate options. That feels much more natural for me.
>> Then you would still need to have some conditional processing but that 
>> could be a simple Java class that picks up the right resources.
>> It's maybe a matter of a taste but introduction of any logic to the 
>> configuration is wrong. Configuration should be always declarative not 
>> imperative, IMHO.
> Hehe, I actually suggested the same approach to the jetspeed people as
> I think it's clearer to have separate files and you just choose at 
> runtime which files to use. But as you say, it's a matter of taste.

yes, I agree with you both. IMHO you have a design problem with your 
application when you have to introduce conditionals in configuration files.

Reinhard Pötz                           Managing Director, {Indoqa} GmbH

Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member        

View raw message