Benjamin Boksa wrote:
Hi List,
attached is a reproducible error I get when using the Cocoon Spring
Configurator 2.0 in stand-alone mode. The idea is to use the
configurator to implement a kind of ServiceLocator which internally uses
Spring and hides away the implementation details from the
Hi Leszek,
thanks you very much for looking into my problem:
I have run your test scenario. Please use the following statement:
configurator:settings
configurator:include-beans dir=classpath*:/META-INF/foo-
service/spring/
configurator:include-properties
Benjamin Boksa wrote:
Is there any recommended dependeny/dependency-exclusion setup to make
cocoon-core utilize the new (2.0.0) spring-configurator? I have tried
several dependency-configurations but was not able to find a working one.
I would be really glad for any help on that point - as
Benjamin Boksa wrote:
Hi Leszek,
thanks you very much for looking into my problem:
I have run your test scenario. Please use the following statement:
configurator:settings
configurator:include-beans
dir=classpath*:/META-INF/foo-service/spring/
Am 12.02.2009 um 14:29 schrieb Leszek Gawron:
Benjamin Boksa wrote:
Hi Leszek,
thanks you very much for looking into my problem:
I have run your test scenario. Please use the following statement:
configurator:settings
configurator:include-beans dir=classpath*:/META-INF/foo-
Benjamin Boksa wrote:
Not sure if I understand you on that one… Let's assume there are two
foo.properties files both containing a property bar - when using the
settings above how does the spring-configurator decide which is the
right property to use? I think this might result in a problem (the
