Hi Bruno Welcome to the Camel community!
AFAIK this a known limitation by Blueprint and there're open JIRA tickets around reporting this. There's a solution I've seen on the SMX user forum which I think can help in your case: http://servicemix.396122.n5.nabble.com/Property-in-OSGi-service-reference-filter-attribute-tp5713964p5715300.html A side note: Camel has also it's own Placeholder support (also for Blueprint as well, fully functional from Camel 2.10.5/2.11.1 onwards) which you could make use of inside your Camel routes: http://camel.apache.org/using-propertyplaceholder.html#UsingPropertyPlaceholder-UsingBlueprintpropertyplaceholderwithCamelroutes Babak bruno.meseguer wrote > Hi, > > I'm new to Camel, and I'm still digesting all the bits and pieces. > > I'm having a problem with the combination Blueprint/Camel, I would say > it's more on the Blueprint side. > First of all could you please confirm you could can help me here with > Blueprint difficulties? > > The problem is the following: > I'm defining an OSGI service and I'm trying to make use of it from an > external Camel context using a reference. > > To do this I need to specify in the reference's filter the version of the > service defined, as follows: > > > <reference id="helper" interface="com.service.helperInterface" > filter="(version=helper_1-0-0)"/> > The version filter is needed as I may have running multiple versions, and > it needs to be configurable, ideally it would look like: > > > <reference id="helper" interface="com.service.helperInterface" > filter="(version={{helper_version}})"/> > The property-placeholder feature from Blueprint does not work here. > > > Thanks in advance, > > Bruno -- View this message in context: http://camel.465427.n5.nabble.com/references-in-Camel-using-Blueprint-tp5733684p5733843.html Sent from the Camel - Users mailing list archive at Nabble.com.
