Re: Mina version
Martin Ritchie a écrit : If you are just looking to remove the backport dependency then swapping to mina 1.1.1 should do that for you. We currently use 1.0.1 which has the dependency as we used to build a Java 1.4 cllent. We don't (and can't) do that now so we should at least upgrade mina to 1.1.1 which is the Java 1.5 version of 1.0.1. I made the change to Mina 1.1.7, the patch is available for review in JIRA: https://issues.apache.org/jira/browse/QPID-2498 Emmanuel Bourg - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Mina version
Martin Ritchie a écrit : If you are just looking to remove the backport dependency then swapping to mina 1.1.1 should do that for you. Thank you Martin. By reading the mailing list archive I was under the impression Qpid required a specific snapshot due to a regression in the recent releases of Mina. We currently use 1.0.1 which has the dependency as we used to build a Java 1.4 cllent. We don't (and can't) do that now so we should at least upgrade mina to 1.1.1 which is the Java 1.5 version of 1.0.1. I'll be pleased to contribute a patch to upgrade Mina and remove backport-util if someone can review and apply it. Emmanuel Bourg - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Mina version
On 1 April 2010 18:18, Emmanuel Bourg wrote: > Rajith Attapattu a écrit : >> >> All though the 0-10 code path doesn't use MINA as the transport, it is >> still required on the client side as the JMS layer is still using the >> Mina byte buffer internally. >> The 0-8 code also uses MINA as the default transport. >> So the client has both compile time and run time dependency on MINA. >> It would good if we could actually get rid of the MINA deps in the >> client side and the transport related code factored out into a >> transport module. >> The client can then load the transport based on reflection (the 0-10 >> code path now does this.) > > I'm just looking at removing the dependency on backport-util for the client, > but removing Mina would be even better. Using Mina makes sense on the server > to improve the scalability, but on the client I guess using classic IO > classes should be enough. > > Emmanuel Bourg Emmanuel, If you are just looking to remove the backport dependency then swapping to mina 1.1.1 should do that for you. We currently use 1.0.1 which has the dependency as we used to build a Java 1.4 cllent. We don't (and can't) do that now so we should at least upgrade mina to 1.1.1 which is the Java 1.5 version of 1.0.1. Hope that helps, Martin > - > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:dev-subscr...@qpid.apache.org > > -- Martin Ritchie - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Mina version
On 04/01/2010 01:18 PM, Emmanuel Bourg wrote: Rajith Attapattu a écrit : All though the 0-10 code path doesn't use MINA as the transport, it is still required on the client side as the JMS layer is still using the Mina byte buffer internally. The 0-8 code also uses MINA as the default transport. So the client has both compile time and run time dependency on MINA. It would good if we could actually get rid of the MINA deps in the client side and the transport related code factored out into a transport module. The client can then load the transport based on reflection (the 0-10 code path now does this.) I'm just looking at removing the dependency on backport-util for the client, but removing Mina would be even better. Using Mina makes sense on the server to improve the scalability, but on the client I guess using classic IO classes should be enough. yes, I believe there is an intention for remove the dependency of mina from the client, and I'm sure help would be appreciated. Carl. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Mina version
Rajith Attapattu a écrit : All though the 0-10 code path doesn't use MINA as the transport, it is still required on the client side as the JMS layer is still using the Mina byte buffer internally. The 0-8 code also uses MINA as the default transport. So the client has both compile time and run time dependency on MINA. It would good if we could actually get rid of the MINA deps in the client side and the transport related code factored out into a transport module. The client can then load the transport based on reflection (the 0-10 code path now does this.) I'm just looking at removing the dependency on backport-util for the client, but removing Mina would be even better. Using Mina makes sense on the server to improve the scalability, but on the client I guess using classic IO classes should be enough. Emmanuel Bourg - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Mina version
All though the 0-10 code path doesn't use MINA as the transport, it is still required on the client side as the JMS layer is still using the Mina byte buffer internally. The 0-8 code also uses MINA as the default transport. So the client has both compile time and run time dependency on MINA. It would good if we could actually get rid of the MINA deps in the client side and the transport related code factored out into a transport module. The client can then load the transport based on reflection (the 0-10 code path now does this.) Regards, Rajith On Thu, Apr 1, 2010 at 10:01 AM, Carl Trieloff wrote: > > > I know mina is no longer required from the client side, someone else will > need to comment on the Java broker > > Carl. > > > On 03/31/2010 02:05 PM, Emmanuel Bourg wrote: >> >> Could someone enlighten me about the Mina version currently used in Qpid >> please? I searched through the messages of the list back to 2006 and found >> this: >> >> >> http://mail-archives.apache.org/mod_mbox/qpid-dev/200612.mbox/%3cc5e632550612010029j3c0beec6p4eeff0aab1d36...@mail.gmail.com%3e >> >> That is, Qpid uses a snapshot version build from the revision 463149 at >> http://svn.apache.org/repos/asf/mina/trunk. >> >> However I also found mention of performance patches that were necessary >> for Qpid. Are they also included in the revision above or were they applied >> separately? >> >> Thank you, >> >> Emmanuel Bourg >> >> - >> Apache Qpid - AMQP Messaging Implementation >> Project: http://qpid.apache.org >> Use/Interact: mailto:dev-subscr...@qpid.apache.org >> > > > - > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:dev-subscr...@qpid.apache.org > > -- Regards, Rajith Attapattu Red Hat http://rajith.2rlabs.com/ - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Mina version
I know mina is no longer required from the client side, someone else will need to comment on the Java broker Carl. On 03/31/2010 02:05 PM, Emmanuel Bourg wrote: Could someone enlighten me about the Mina version currently used in Qpid please? I searched through the messages of the list back to 2006 and found this: http://mail-archives.apache.org/mod_mbox/qpid-dev/200612.mbox/%3cc5e632550612010029j3c0beec6p4eeff0aab1d36...@mail.gmail.com%3e That is, Qpid uses a snapshot version build from the revision 463149 at http://svn.apache.org/repos/asf/mina/trunk. However I also found mention of performance patches that were necessary for Qpid. Are they also included in the revision above or were they applied separately? Thank you, Emmanuel Bourg - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Mina version
Could someone enlighten me about the Mina version currently used in Qpid please? I searched through the messages of the list back to 2006 and found this: http://mail-archives.apache.org/mod_mbox/qpid-dev/200612.mbox/%3cc5e632550612010029j3c0beec6p4eeff0aab1d36...@mail.gmail.com%3e That is, Qpid uses a snapshot version build from the revision 463149 at http://svn.apache.org/repos/asf/mina/trunk. However I also found mention of performance patches that were necessary for Qpid. Are they also included in the revision above or were they applied separately? Thank you, Emmanuel Bourg - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
