Hi,

We were trying to use camel-azure-storage-queue component in a blueprint xml 
and get it to work on Karaf AKS.
Karaf 4.3.3 and Camel 3.11.4 is used.

Blueprint xml snippet:
<toD 
uri="azure-storage-queue://{{account_name}}/{{queue_name}}?accessKey={{key}}"/>



For some reason, to get it to work we need to both feature install a camel 
project and Karaf commands, although we saw some of the bundles are duplicated.
feature.xml installed:
    <feature name=" my-poc" version="1.0-SNAPSHOT">
        <feature>camel</feature>
        <feature>camel-blueprint</feature>
        <feature>camel-azure-storage-queue</feature>

        
<bundle>mvn:org.apache.aries.spifly/org.apache.aries.spifly.dynamic.bundle/1.2.4</bundle>
        
<bundle>wrap:mvn:com.azure/azure-core-http-netty/1.11.1$Require-Capability=osgi.extender;filter:="(osgi.extender=osgi.serviceloader.registrar)"&amp;Provide-Capability=osgi.serviceloader;osgi.serviceloader=com.azure.core.implementation.http.HttpClientProvider</bundle>
        
<bundle>wrap:mvn:com.azure/azure-core/1.21.0$Require-Capability=osgi.extender;filter:="(osgi.extender=osgi.serviceloader.processor)",osgi.serviceloader;filter:="(osgi.serviceloader=com.azure.core.implementation.http.HttpClientProvider)";cardinality:=multiple</bundle>
        <bundle>mvn:io.projectreactor.netty/reactor-netty-http/1.0.12</bundle>
        
<bundle>mvn:io.netty/netty-transport-native-unix-common/4.1.68.Final</bundle>
        <bundle>mvn:io.projectreactor.netty/reactor-netty-core/1.0.12</bundle>
        <bundle>mvn:io.netty/netty-transport-native-epoll/4.1.68.Final</bundle>
        <bundle>mvn:io.netty/netty-resolver-dns/4.1.68.Final</bundle>
        <bundle>mvn:io.netty/netty-codec-dns/4.1.68.Final</bundle>
        <bundle>mvn:io.netty/netty-buffer/4.1.68.Final</bundle>
        <bundle>mvn:io.netty/netty-common/4.1.68.Final</bundle>
        <bundle>mvn:io.netty/netty-transport/4.1.68.Final</bundle>
        <bundle>mvn:io.netty/netty-resolver/4.1.68.Final</bundle>
        <bundle>mvn:io.netty/netty-handler/4.1.68.Final</bundle>
        <bundle>mvn:io.netty/netty-codec/4.1.68.Final</bundle>
        <bundle>mvn:io.netty/netty-codec-http/4.1.68.Final</bundle>
        <bundle>mvn:io.netty/netty-codec-http2/4.1.68.Final</bundle>
        <bundle>mvn:io.netty/netty-handler-proxy/4.1.68.Final</bundle>
        <bundle>mvn:io.netty/netty-codec-socks/4.1.68.Final</bundle>
        <bundle>mvn:com.my.project/my-poc/1.0-SNAPSHOT</bundle>
    </feature>


karaf commands needed:
karaf@root()> bundle:install -s 
wrap:mvn:com.azure/azure-core-http-netty/1.11.1\$Require-Capability=osgi.extender\;filter:=\"(osgi.extender=osgi.serviceloader.registrar)\"\&Provide-Capability=osgi.serviceloader\;osgi.serviceloader=com.azure.core.http.HttpClientProvider
karaf@root()> bundle:install -s 
wrap:mvn:com.azure/azure-core/1.21.0\$Require-Capability=osgi.extender\;filter:=\"(osgi.extender=osgi.serviceloader.processor)\",osgi.serviceloader\;filter:=\"(osgi.serviceloader=com.azure.core.http.HttpClientProvider)\"\;cardinality:=multiple
karaf@root()> bundle:install -s 
mvn:org.apache.aries.spifly/org.apache.aries.spifly.dynamic.bundle/1.2.4



if we just apply either one, say if we only feature install the camel project 
but not run the Karaf commands above, it won't work. (Even if we know the 
bundles are already included in feature.xml)

Is it because of how wrap scheme is handled?
Or is it related to service loader mediator using apache.aries.spifly on Karaf?
Is there any rule of thumb resolving bundles in OSGI env? How can we get this 
to work easier?


Many thanks,
Ivan





[cid:image001.jpg@01D807DA.DDFE38C0]

Ivan Tam
Engr 2, Software Eng
Software Engineering

ivan....@bd.com

10020 Pacific Mesa Blvd
San Diego, California, 92121
US
t: (858)617.1556

bd.com<http://www.bd.com/>

[cid:image002.jpg@01D807DA.DDFE38C0]


*******************************************************************
IMPORTANT MESSAGE FOR RECIPIENTS IN THE U.S.A.:
This message may constitute an advertisement of a BD group's products or 
services or a solicitation of interest in them. If this is such a message and 
you would like to opt out of receiving future advertisements or solicitations 
from this BD group, please forward this e-mail to optoutbygr...@bd.com. 
[BD.v1.0]
*******************************************************************
This message (which includes any attachments) is intended only for the 
designated recipient(s). It may contain confidential or proprietary information 
and may be subject to the attorney-client privilege or other confidentiality 
protections. If you are not a designated recipient, you may not review, use, 
copy or distribute this message. If you received this in error, please notify 
the sender by reply e-mail and delete this message. Thank you.
*******************************************************************
Corporate Headquarters Mailing Address: BD (Becton, Dickinson and Company) 1 
Becton Drive Franklin Lakes, NJ 07417 U.S.A.

Reply via email to