Fuse ESB/OSGI/Blueprint reading configuration files alphabetically?

[minibiti]

Hello,

I experience something rather strange and I would like to know if other people have experienced the same...

I am currently working on a project using jboss fuse (previously fuse esb) and we are using blueprint for our configuration files.

We use property place holders and have the following files under src/main/resources/OSGI-INF/blueprint:

blueprint.xml

properties.xml

In blueprint.xml we have something like this:

<bean id="myBean" class="com.test.MyClass">

        <property name="prop1" value="${my.prop}" />

<∕bean>

Then in properties.xml I have this:

    <cm:property-placeholder persistent-id="my.properties" update-strategy="reload">

        <cm:default-properties>

            <cm:property name="my.prop" value="true" />

        </cm:default-properties>

    </cm:property-placeholder>

And I obviously have a setter for prop1 (which is a String) in MyClass.

But what I see is that when I deploy this, prop1 is set to "${my.prop}" instead of "true", i.e the variable never gets replaced with its defined value!

But now if I call the properties file aaa_properties.xml, it works!!

Is this a bug in the blueprint container?

Did any one else experience the same behaviour?

Thanks for your feedback

JM.

[roybrumby]

Hi JM,

I just found your post after posting a slightly different one but with possibly the same underlying reason.

Please see my post at Blueprint Bundle with Metatype deployment problem

Maybe it will give you some ideas - there is a workaround I founf which might help you too.

Roy

[roybrumby]

Hi JM,

I have seen the same behaviour. The property name is used when the value cannot be resolved. I'm not sure what you mean when you say it works when you call your properties file. Are you importing the properties file in your blueprint? I suspect that may be what is missing.

Roy