Re: Missing capability for camel-blueprint Karaf feature

[Benjamin Graf]

Hi JB;

please consider to backport missing header to actual 3.11.x LTS, too.

Regards,

Benjamin

On 06.10.2021 09:50, Jean-Baptiste Onofre wrote:

I mean: “waiting camel-blueprint bundle improvement (adding missing capability 
header)”

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 it’s 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

OpenPGP_signature
Description: OpenPGP digital signature