camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sunil Pandit <>
Subject Re: OSGI Service reference in Camel Context
Date Mon, 10 Dec 2012 03:32:57 GMT
Thanks for your response. Yes I want to use Blueprint . I am not sure how I
can do in Java code . Do you mean registering servicetracker ?

The filter or the placeholder is supported in service registration but not
in servicereference.

Sunil Pandit

200 West Cesar Chavez., Austin, TX 78701
Financial Services Sector  |  p: +1-512-2755792 |  |

This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of e-mail
for such purpose.

From:	"Claus Ibsen-2 [via Camel]" <ml-node
To:	Sunil Pandit/USA/CSC@CSC
Date:	12/09/2012 08:02 AM
Subject:	Re: OSGI Service reference in Camel Context


This is really an area of OSGi Blueprint and what it supports.
And possible if Apache Aries Blueprint has some extensions to support
placeholders in filters etc.

You can use Java code to refer to a osgi service with a dynamic filter.
But I guess you want to do this in the blueprint XML file instead?

On Thu, Dec 6, 2012 at 7:35 PM, Sunil Pandit <[hidden email]> wrote:

> Hi All ,
> I am using FUSE ESB . I have a OSGI service registered in service
> and have a camel context which has a service reference . The service
> reference specifies an interface and a filter . Everything works fine
> the filter  has hardcoded value in the camel context route . Such as
> =(" =xyz ").
> What we are trying to do is dynamically provide this filter value
> Camel Context can  resolve this reference dynamically . I have tried
> property place holder and read a property , but it seems that the filter
> does not process anything other than string .
> So my question is what is the other way  to dynamically resolve a service

> from camel context. I need to resolve the service on two criteria one is
> interface and other is  property with which that service was registered
> the service registry.
> Thanks
> Sunil
> --
> View this message in context:

> Sent from the Camel - Users mailing list archive at

Claus Ibsen
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: [hidden email]
Twitter: davsclaus
Author of Camel in Action:

If you reply to this email, your message will be added to the discussion

To unsubscribe from OSGI Service reference in Camel Context, click here.

View this message in context:
Sent from the Camel - Users mailing list archive at
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message