Sorry, forget to say, in osgi registry, the name of service(bean) is the osgi service's class name; that's to say to using "to" endpoint to invoke a osgi service is not like to invoke a spring bean. It should use the class as name , not the id like spring registry does;
By the way, if you osgi service is dynamic while camel is running, you cannot use the osgi registry safely, because camel doesn't tracking the osgi service correctly (at least in camel 2.4.0) =========================================================================== Trying recipient-list pattern(dynamic to create to endpoint to invoke beans in registry), it will look registry of osgi first(Clause has already said ) -----original ----- Sender: klausb [mailto:[email protected]] Date: 2010/12/14 23:31 Sender: [email protected] Subject: Re: How to setup a dynamic route using beans in Java w/o having a spring ref to them? Hi Claus, I tried it, but it doesn't work. The point is, that my dynamic Java-DSL route-builder does not know, what the IDs of the beans are, which are added to the routes. It works, if I'm adding the osgi:ref to one of the spring resource files, like this: <osgi:reference id="myBean" interface="com.corp.MyIF"/> Without this line, the bean is not found inside a bean step like this: .to("bean:${beanName}?method=collect"), where beanName=myBean. This is the dynamic part of this route-builder (Groovy string). What I'm looking for is a way to do the lookup like <osgi:ref...> statement in my Java code during route construction. klaus. -- View this message in context: http://camel.465427.n5.nabble.com/How-to-setup-a-dynamic-route-using-beans-i n-Java-w-o-having-a-spring-ref-to-them-tp3304398p3304754.html Sent from the Camel - Users mailing list archive at Nabble.com.
