You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Henryk Konsek <he...@gmail.com> on 2015/11/28 22:36:44 UTC
Upgrading AMQP component to qpid-jms-client
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 (which supports both AMQP
0.9 and 1.0) however some users complain about its quality compared to the
latest qpid-jms-client. Unfortunately the latest version of qpid-jms-client
supports only AMQP 1.0.
Do you want me to upgrade camel-amqp to the latest qpid-jms-client (and
therefore drop support to AMQP 0.9) or create a new component (like
camel-amqp2) using latest qpid-jms-client and supporting only AMQP 1.0?
Cheers!
[1] http://qpid.apache.org/components/jms/
--
Henryk Konsek
http://about.me/hekonsek
Re: Upgrading AMQP component to qpid-jms-client
Posted by Henryk Konsek <he...@gmail.com>.
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 ServiceMix recently?
Only proton-j?
Cheers!
[1] https://issues.apache.org/jira/browse/CAMEL-9381
[2]
https://github.com/apache/camel/blob/master/platforms/karaf/features/src/main/resources/features.xml#L84-L86
wt., 1.12.2015 o 14:39 użytkownik Henryk Konsek <he...@gmail.com>
napisał:
> Awesome, Christan! I will start working on this soon.
>
> Cheers!
>
> On Tue, Dec 1, 2015, 14:08 Christian Schneider <ch...@die-schneider.net>
> wrote:
>
>> Hi Henryk,
>>
>> I just helped JB to get the servicemix qpid release out.
>>
>> The release will be
>> "mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.qpid/0.32_3".
>> It is currently under vote.
>> You can already try the snapshot
>> "mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.qpid/0.32_3-SNAPSHOT".
>>
>> Christian
>>
>>
>>
>> On 30.11.2015 09:36, Henryk Konsek wrote:
>>
>> 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 <
>> chris@die-schneider.net> napisał:
>>
>>> I would like to get the wrapping out of Artemis before the next release
>>> We have at least one customer where it would be a problem as the only
>>> allow signed bundles in their system.
>>>
>>> In the worst case I think it would not hurt much to have the wrap in the
>>> next release but we should try to replace it with a proper bundle as soon
>>> as possible.
>>>
>>>
>>> Christian
>>>
>>>
>>> Am 29.11.2015 um 21:33 schrieb Henryk Konsek:
>>>
>>> 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 Christian Schneider <
>>> chris@die-schneider.net> napisał:
>>>
>>>> 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 missing bundles:
>>>>
>>>> https://github.com/apache/activemq-artemis/blob/master/artemis-features/src/main/resources/features.xml#L53-L54
>>>>
>>>> Christian
>>>>
>>>> Am 29.11.2015 um 09:37 schrieb Andrea Cosentino:
>>>> > I think upgrade is the better solution.
>>>> >
>>>> > Thanks Henryk :-)
>>>> >
>>>>
>>>> --
>>> Henryk Konsek
>>> http://about.me/hekonsek
>>>
>>>
>>> --
>> Henryk Konsek
>> http://about.me/hekonsek
>>
>>
>>
>> --
>> Christian Schneiderhttp://www.liquid-reality.de
>>
>> Open Source Architecthttp://www.talend.com
>>
>> --
> Henryk Konsek
> http://about.me/hekonsek
>
--
Henryk Konsek
http://about.me/hekonsek
Re: Upgrading AMQP component to qpid-jms-client
Posted by Henryk Konsek <he...@gmail.com>.
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 <
chris@die-schneider.net> napisał:
> I would like to get the wrapping out of Artemis before the next release
> We have at least one customer where it would be a problem as the only
> allow signed bundles in their system.
>
> In the worst case I think it would not hurt much to have the wrap in the
> next release but we should try to replace it with a proper bundle as soon
> as possible.
>
>
> Christian
>
>
> Am 29.11.2015 um 21:33 schrieb Henryk Konsek:
>
> 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 Christian Schneider <
> chris@die-schneider.net> napisał:
>
>> 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 missing bundles:
>>
>> https://github.com/apache/activemq-artemis/blob/master/artemis-features/src/main/resources/features.xml#L53-L54
>>
>> Christian
>>
>> Am 29.11.2015 um 09:37 schrieb Andrea Cosentino:
>> > I think upgrade is the better solution.
>> >
>> > Thanks Henryk :-)
>> >
>>
>> --
> Henryk Konsek
> http://about.me/hekonsek
>
>
> --
Henryk Konsek
http://about.me/hekonsek
Re: Upgrading AMQP component to qpid-jms-client
Posted by Henryk Konsek <he...@gmail.com>.
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 Christian Schneider <
chris@die-schneider.net> napisał:
> 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 missing bundles:
>
> https://github.com/apache/activemq-artemis/blob/master/artemis-features/src/main/resources/features.xml#L53-L54
>
> Christian
>
> Am 29.11.2015 um 09:37 schrieb Andrea Cosentino:
> > I think upgrade is the better solution.
> >
> > Thanks Henryk :-)
> >
>
> --
Henryk Konsek
http://about.me/hekonsek
Re: Upgrading AMQP component to qpid-jms-client
Posted by Christian Schneider <ch...@die-schneider.net>.
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 missing bundles:
https://github.com/apache/activemq-artemis/blob/master/artemis-features/src/main/resources/features.xml#L53-L54
Christian
Am 29.11.2015 um 09:37 schrieb Andrea Cosentino:
> I think upgrade is the better solution.
>
> Thanks Henryk :-)
>
Re: Upgrading AMQP component to qpid-jms-client
Posted by Andrea Cosentino <an...@yahoo.com.INVALID>.
I think upgrade is the better solution.
Thanks Henryk :-)
--
Andrea Cosentino
---------------------------------
Apache Camel PMC Member
Email: ancosen1985@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Sunday, November 29, 2015 9:18 AM, Claus Ibsen <cl...@gmail.com> wrote:
+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 <he...@gmail.com> 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 (which supports both AMQP
> 0.9 and 1.0) however some users complain about its quality compared to the
> latest qpid-jms-client. Unfortunately the latest version of qpid-jms-client
> supports only AMQP 1.0.
>
> Do you want me to upgrade camel-amqp to the latest qpid-jms-client (and
> therefore drop support to AMQP 0.9) or create a new component (like
> camel-amqp2) using latest qpid-jms-client and supporting only AMQP 1.0?
>
> Cheers!
>
> [1] http://qpid.apache.org/components/jms/
> --
> Henryk Konsek
> http://about.me/hekonsek
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: Upgrading AMQP component to qpid-jms-client
Posted by Claus Ibsen <cl...@gmail.com>.
+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 <he...@gmail.com> 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 (which supports both AMQP
> 0.9 and 1.0) however some users complain about its quality compared to the
> latest qpid-jms-client. Unfortunately the latest version of qpid-jms-client
> supports only AMQP 1.0.
>
> Do you want me to upgrade camel-amqp to the latest qpid-jms-client (and
> therefore drop support to AMQP 0.9) or create a new component (like
> camel-amqp2) using latest qpid-jms-client and supporting only AMQP 1.0?
>
> Cheers!
>
> [1] http://qpid.apache.org/components/jms/
> --
> Henryk Konsek
> http://about.me/hekonsek
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2