On Wed, 30 Aug 2006, Carsten Ziegeler wrote:
Date: Wed, 30 Aug 2006 22:00:13 +0200
From: Carsten Ziegeler <[EMAIL PROTECTED]>
Reply-To: dev@cocoon.apache.org
To: dev@cocoon.apache.org
Subject: Re: Property replacement in spring config files
Giacomo Pati wrote:
Hi all
I couldn't follow all the recent changes to the property/settings
subject but it seems with the current trunk not all properties will be
replaced anymore in spring config files.
I have spring.xml where the class attribute of a bean element is set by
a property and this has worked util today (well, my last full build of
trunk was mid last week).
Is this change because of some refactoring or something else?
I guess it is due to the refactoring, but I'm not sure. The difference
between the "old" version and today is that now Spring is duing the
replacement for us. This means now we are reading the configurations
path them to Spring and tell Spring to replace the properties.
Is it possible to use a property as class name in "plain" spring?
Good question. Never used "plain" Spring that way, but
Cocoon-Spring-Integration ;-) and I loved being able to do it. That way I
was able to have "Mock"-Beans for mode=dev (speed), "Local"-Beans for
mode=test (functional), and "Prod"-Beans for mode=prod (live) just with a
set of properties no need to change/filter any config file.
Ciao and thanks
--
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
