After We did feature:install camel-azure-storage-queue, we saw bundle:list
already included the SMX bundles.
123 | Active | 50 | 1.16.0.1 | Apache ServiceMix :: Bundles ::
azure-core
124 | Active | 50 | 12.12.0.1 | Apache ServiceMix :: Bundles ::
azure-storage-common
125 | Active | 50 | 12.10.0.1 | Apache ServiceMix :: Bundles ::
azure-storage-queue
126 | Active | 10 | 2.3.1.1 | Apache ServiceMix :: Bundles ::
jaxb-runtime
127 | Active | 10 | 2.9.0 | Apache ServiceMix :: Specs ::
Activation API 1.4
But we still saw the exception from azure lib when running the blueprint.
545 Caused by: org.apache.camel.RuntimeCamelException:
java.lang.IllegalStateException: A request was made to load the default
HttpClie 545 nt provider but one could not be found on the classpath. If you
are using a dependency manager, consider including a dependency on
545 azure-core-http-netty or azure-core-http-okhttp. Depending on your
existing dependencies, you have the choice of Netty or OkHttp im 545
plementations. Additionally, refer to
https://aka.ms/azsdk/java/docs/custom-httpclient to learn about writing your
own implementati 545 on.
Does SMX bundles include all the dependencies of azure-storage-queue ?
Thanks,
Ivan
-----Original Message-----
From: Jean-Baptiste Onofré <[email protected]>
Sent: Thursday, January 13, 2022 12:12 AM
To: [email protected]
Subject: Re: getting camel-azure-storage-queue component to work on Karaf
EXTERNAL EMAIL - Use caution opening attachments and links.
Hi,
Any reason why not using SMX azure bundles ? I created them for Camel
components.
If you need additional bundles or updated versions, please let me know.
Regards
JB
On 13/01/2022 05:59, Ivan Tam wrote:
> 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.bu
> ndle/1.2.4</bundle>
>
>
> <bundle>wrap:mvn:com.azure/azure-core-http-netty/1.11.1$Require-Capabi
> lity=osgi.extender;filter:="(osgi.extender=osgi.serviceloader.registra
> r)"&Provide-Capability=osgi.serviceloader;osgi.serviceloader=com.a
> zure.core.implementation.http.HttpClientProvider</bundle>
>
>
> <bundle>wrap:mvn:com.azure/azure-core/1.21.0$Require-Capability=osgi.e
> xtender;filter:="(osgi.extender=osgi.serviceloader.processor)",osgi.se
> rviceloader;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=os
> gi.extender\;filter:=\"(osgi.extender=osgi.serviceloader.registrar)\"\
> &Provide-Capability=osgi.serviceloader\;osgi.serviceloader=com.azure.c
> ore.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.servic
> eloader\;filter:=\"(osgi.serviceloader=com.azure.core.http.HttpClientP
> rovider)\"\;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
>
>
>
> *Ivan Tam*
> /Engr 2, Software Eng/
> /Software Engineering/
>
> [email protected]
>
> 10020 Pacific Mesa Blvd
> San Diego, California, 92121
> US
> *t: *(858)617.1556
>
> *bd.com* <http://www.bd.com/>
>
> *******************************************************************
> 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 [email protected]. [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.
>
