Done [1]. I have also improved documentation and tests coverage.
For now we have to wrap the following three [2] jars:
wrap:mvn:org.apache.qpid/qpid-jms-client
wrap:mvn:org.apache.qpid/proton-j/0.10
wrap:mvn:io.netty/netty-all/4.0.17.Final
Christian, which of those jars have you included in Serv
Understood.
I will proceed with an upgrade then and use wrap for a while. Then when
you're done with ServiceMix bundle, I will replace the wrappings.
I will let you know when I'm done with an upgrade.
pon., 30.11.2015 o 09:33 użytkownik Christian Schneider <
ch...@die-schneider.net> napisał:
>
Hi,
Yes, qpid-jms-client requires org.apache.qpid:proton-j:jar:0.10. I guess we
can just wrap it until ServiceMix is out, right? (the same way it is done
for Artemis)
If this wrapping is no problem for you, I will start the upgrade tomorrow.
Cheers!
niedz., 29.11.2015 o 11:35 użytkownik Christ
Not sure if this is the same situation as with the Artemis amqp support.
There I had the problem that some of the new qpid libraries are not yet
OSGi bundles.
JB wanted to include them in the next servicemix release. So we could
probably also use these for camel.
For reference. These are the
I think upgrade is the better solution.
Thanks Henryk :-)
--
Andrea Cosentino
-
Apache Camel PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Sunday, November 29, 2015 9:18 AM, Claus Ibsen wrote:
+1 to upgrade.
0.9 users are usi
+1 to upgrade.
0.9 users are using rabbitmq and can use camel-rabbitmq which is the
better module to use.
On Sat, Nov 28, 2015 at 10:36 PM, Henryk Konsek wrote:
> Hi,
>
> I'd like to upgrade AMQP component to use the latest qpid-jms client [1].
>
> Currently we use older qpid-amqp-1-0-client-jms
