Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (athena.apache.org: domain of grek@tuffmail.com designates
 216.86.168.178 as permitted sender)
Message-ID: <487CA5A5.6010201@tuffmail.com>
Date: Tue, 15 Jul 2008 15:27:01 +0200
From: Grzegorz Kossakowski <grek@tuffmail.com>
User-Agent: Thunderbird 2.0.0.12 (X11/20071114)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Spring Configurator - filter/include strategy
References: <487C9AA6.4020004@tuffmail.com> <487C9F12.9000808@apache.org>
In-Reply-To: <487C9F12.9000808@apache.org>
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 7bit

Carsten Ziegeler pisze:
> Hi,
> 
> I'm not sure what the best way is - but the jetspeed folks followed a 
> different road and added conditionals inside the configuration files.
> So only if a criteria is met something is added. I tried to convince 
> them to use the spring configurator and add the logic here...
> So perhaps this is something we could add on top of the configurator now?

Hi Carsten,

I fail to follow you on your answer so I have a couple of questions:
1. What logic you wanted to added "here"? Support for some syntax of conditional includes? If so, 
how this would look like?
2. What do you mean by adding something on top of configurator?
3. What's your opinion about my proposal itself?

I'm really with you when it comes to increasing number of users of Spring Configurator but I need 
little bit more clear strategy here. ;-)

-- 
Best regards,
Grzegorz Kossakowski