Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <45262B01.7090601@apache.org>
Date: Fri, 06 Oct 2006 12:08:01 +0200
From: Carsten Ziegeler <cziegeler@apache.org>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: [2.2] Spring 2.0 final and property handling
References: <4526258E.4020001@apache.org> <4526263E.5000105@apache.org>
In-Reply-To: <4526263E.5000105@apache.org>
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit

Reinhard Poetz wrote:
> 
> hmm, why do we have another mechanism for setting properties now?. can't we put 
> in all properties into WEB-INF/cocoon/properties?
> 
This was actually my first implementation, but I think there is a
difference between properties which you might want to use for anything
and a mechanism for overriding the configuration of your beans. The
latter is also just for spring (and Avalon).

So we have:
WEB-INF/cocoon/properties - with any properties :)
WEB-INF/cocoon/spring/*.xml         Spring bean definitions
WEB-INF/cocoon/spring/*.properties  Spring bean configurations

The difference might be subtle but I think we should keep this separate.
But of course this is not carved in stone yet, so we can change it in
every way we can agree on.

Carsten
-- 
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/