<reference> filter and "managed" properties

[mvanorman]

Is there a way to have a service "reference" be re-looked up in cases where the filter expression references a property in configurationadmin that has changed? I'm doing something along the lines of:

<reference... filter="${filter}"/>

and would like to be able to dynamically modify the value of ${filter} and have the service reference be re-resolved.

Thanks,
Michael.

[fkh]

Hi Michael,

have you already found a solution for your problem? In case you did, could you please tell me how you achieved this?

fkh

[mvanorman]

No, I have not found a solution to this.

[Costin Leau]

You could use a PropertyPlaceholderConfigurer to do replacement or use SpEL in Spring 3.0 for dynamic evaluations.

[mvanorman]

That's not the problem. I've done that. However, in the OSGi environment, I can get my other beans to respond to changes in a properties file at runtime using managed properties. But the filter expression for a service reference does not get notified when the properties change like other beans do.

[Costin Leau]

Right - the filter is static and that's on purpose since the idea is to track services that follow a "static" criteria. If the criteria is dynamic, then the problem gets complicated since the filter can have class/service constraints that are incompatible with the service tracking proxy.