Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <45262BA3.6040301@otego.com>
Date: Fri, 06 Oct 2006 12:10:43 +0200
From: Felix Knecht <felix@otego.com>
User-Agent: Thunderbird 1.5.0.7 (X11/20060926)
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>
 <45262B01.7090601@apache.org>
In-Reply-To: <45262B01.7090601@apache.org>
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Carsten Ziegeler schrieb:
> 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

How about the different environments (prod/dev/test) for spring bean
configuration? WIll they go to ../cocoon/properties directory or do we
need a ../cocoon/spring/properties directory as well?

Felix

>
> 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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFJiui2lZVCB08qHERAuz0AKDpbOvRW9RITxi3Vp8trhWzIEnXWQCeL0Kq
+nbwfFU7aM47Y/IJAHMdNwY=
=6R13
-----END PGP SIGNATURE-----