Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Message-Id: <2D67005C-5025-4B15-9FF7-78969212F2E1@boksa.de>
From: Benjamin Boksa <mailinglists@boksa.de>
To: dev@cocoon.apache.org
In-Reply-To: <49942424.9040508@mobilebox.pl>
Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Re: Bug in Cocoon Spring Configurator 2.0 (!?)
Date: Thu, 12 Feb 2009 15:03:44 +0100
References: <FEF49EE3-B6F2-4806-9C4E-2F2DF7BE1439@boksa.de>
 <4993F8D6.7050802@mobilebox.pl>
 <DB53D476-9B8A-4F57-97C3-495F84586384@boksa.de>
 <49942424.9040508@mobilebox.pl>

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=3D"classpath*:/META-INF/foo-=20=

>>>> service/spring"/>
>>>>      <configurator:include-properties dir=3D"classpath*:/META-INF/=20=

>>>> foo-service/properties"/>
>>>>    </configurator:settings>
>>>
>>> using classpath*: ensures that spring will scan all available jars =20=

>>> for that path and aggregate the results.
>> That (scanning all jars) actually was one of the things I tried to =20=

>> avoid (as this might cause problems with the same directories =20
>> existing in two jars). Not very likely, I know, but avoidable as =20
>> the configurator test-case shows.
>
> One more comment: there is completely no problem if every jar has /=20
> META-INF/properties/application.properties file. Every file has =20
> unique URL and the property placeholder will pick all of them. Treat =20=

> it more like a nice feature than a problem :)

Not sure if I understand you on that one=85 Let's assume there are two =20=

"foo.properties" files both containing a property "bar" - when using =20
the settings above how does the spring-configurator decide which is =20
the right property to use? I think this might result in a problem (the =20=

wrong "bar"-property is used)=85

However the big problem/misunderstanding/bug is that with my the =20
original settings

    <configurator:settings>
      <configurator:include-beans dir=3D"/META-INF/foo-service/spring"/>
      <configurator:include-properties dir=3D"META-INF/foo-service/=20
properties"/>
    </configurator:settings>

the bean definitions seem to be read correctly while the properties =20
are not - which I absolutely can't understand. I feel a bit like going =20=

in circles and can't find any good resources (despite of Leszek ;-) ) =20=

which might help me solve this problem.

So if you have further information please let me know :-)

Thanks for you time

Benjamin=