My bad, I thought it was on the karaf dev mailing list :) Regards JB
> Le 6 oct. 2021 à 09:53, benjamin.g...@gmx.net a écrit : > > Hi JB, > > that's why I wrote to the Camel-dev list. ;-) > > Regards, > Benjamin > > On 06.10.21 09:51, Jean-Baptiste Onofre <j...@nanthrax.net> wrote: >> By the way, its not really a Karaf issue but more a camel-karat issue. >> >> So I will add this there :) >> >> Regards >> JB >> >> > Le 6 oct. 2021 � 09:14, JB Onofr� <j...@nanthrax.net> a �crit : >> > >> > Hi >> > >> > The capability should be provided by the bundle. However as its not the >> > case, waiting improvement in Aries blueprint, the feature should provide >> > it. >> > >> > I will do it for 4.3.4 (the release will happen very soon). >> > >> > Regards >> > JB >> > >> >> Le 6 oct. 2021 � 09:01, Benjamin Graf <benjamin.g...@gmx.net> a �crit : >> >> >> >> �Hi, >> >> >> >> I've a Karaf based distribution with bundles containing Camel routes >> >> based on Aries blueprint. If I deploy them via deploy folder everything >> >> works fine but via Karaf feature files I need to put a capability for the >> >> Camel blueprint namespace to avoid resolve error on startup: >> >> >> >> <capability> >> >> osgi.service;objectClass=org.apache.aries.blueprint.NamespaceHandler;effective:=active;osgi.service.blueprint.namespace=http://camel.apache.org/schema/blueprint >> >> </capability> >> >> >> >> Maybe this is missing in 'camel-blueprint' feature? >> >> >> >> Regards >> >> >> >> Benjamin >> >> >> > >> >>
