Thanks for your reply, maybe it's a problem of the eclipse virgo server.
I found several discussions about the META-INF/services FactoryFinder pattern: http://blog.osgi.org/, http://www.osgi.org/download/osgi-early-draft-2011-09.pdf and it's not in http://www.osgi.org/Download/File?url=/download/r5/osgi.core-5.0.0.pdf but only in http://www.osgi.org/Download/File?url=/download/r5/osgi.enterprise-5.0.0.pdf. Maybe it's not (yet) implemented by the virgo-server. Camel seems to be manly used with Karaf as osgi container. Another workaround seems to be declaring a spring bean of the component type with the component's name as you would do with component "jms" which is usually parameterized with configuration. My route is declard as follows: The MANIFEST.MF of the bundle looks like: -- View this message in context: http://camel.465427.n5.nabble.com/Camel-and-osgi-component-not-found-tp5730484p5730492.html Sent from the Camel - Users mailing list archive at Nabble.com.
