You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Benjamin Graf <be...@gmx.net> on 2021/10/06 07:01:18 UTC
Missing capability for camel-blueprint Karaf feature
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
Re: Missing capability for camel-blueprint Karaf feature
Posted by Jean-Baptiste Onofre <jb...@nanthrax.net>.
+1
Regards
JB
> Le 6 oct. 2021 à 10:07, Benjamin Graf <be...@gmx.net> a écrit :
>
> 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é <jb...@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 <be...@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
>>>>
Re: Missing capability for camel-blueprint Karaf feature
Posted by Benjamin Graf <be...@gmx.net>.
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é <jb...@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 <be...@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
>>>
Re: Missing capability for camel-blueprint Karaf feature
Posted by Jean-Baptiste Onofre <jb...@nanthrax.net>.
I mean: “waiting camel-blueprint bundle improvement (adding missing capability header)”
Regards
JB
> Le 6 oct. 2021 à 09:14, JB Onofré <jb...@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 <be...@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
>>
>
Re: Missing capability for camel-blueprint Karaf feature
Posted by Jean-Baptiste Onofre <jb...@nanthrax.net>.
My bad, I thought it was on the karaf dev mailing list :)
Regards
JB
> Le 6 oct. 2021 à 09:53, benjamin.graf@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 <jb...@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� <jb...@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 <be...@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
>> >>
>> >
>>
>>
Re: Missing capability for camel-blueprint Karaf feature
Posted by be...@gmx.net.
Hi JB,
that's why I wrote to the Camel-dev list. ;-)
Regards,
Benjamin
On 06.10.21 09:51, Jean-Baptiste Onofre <jb...@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� <jb...@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 <be...@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
> >>
> >
>
>
Re: Missing capability for camel-blueprint Karaf feature
Posted by Jean-Baptiste Onofre <jb...@nanthrax.net>.
By the way, it’s 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é <jb...@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 <be...@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
>>
>
Re: Missing capability for camel-blueprint Karaf feature
Posted by JB Onofré <jb...@nanthrax.net>.
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 <be...@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
>