Hi all,
As many of you know, there is work going on within Qpid towards creating a
new AMQP 1.0 JMS client based around Proton and implementing a JMS mapping
for AMQP as being documented by the OASIS AMQP Bindings Mappings TC.
Timothy Bish, one of the committers/PMC members at the Apache ActiveMQ
project, is going to join me working on this effort going forward.
Tim has previously done a lot of work on an JMS 1.1 AMQP 1.0 client using
Proton for AMQP 1.0 support, with his existing code being available at
https://github.com/tabish121/NeutronJMS/tree/amqp-only. The code base is
markedly further along in terms of the wider client such as
Connection/Session/Producers/Consumers when compared to the existing work
here at Qpid, which has concentrated initially more on message
implementation and mapping.
We envisage merging our existing work to arrive at the best of both, and
would like to begin doing so within the Qpid project by adding all the
existing code to http://svn.apache.org/viewvc/qpid/jms/trunk/ and then
going forward from there to merge the pieces and work toward tidying things
up and completing remaining areas. Those looking around the code on Github
may spot its previous prototype multi-protocol support; we are only
intending AMQP 1.0 protocol support going forward. Everything is under the
Apache Licence v2, and Tim obviously has an ICLA from his ActiveMQ
participation.
We may also want to think about using Git for our SCM for the JMS work, as
it is a distinct tree and would likely make life easier for collaborating
so extensively with a non-committer.
I just wanted to give a heads up on our thinking and solicit opinion on the
matter before doing anything. Thoughts?
Regards,
Robbie
As many of you know, there is work going on within Qpid towards creating a
new AMQP 1.0 JMS client based around Proton and implementing a JMS mapping
for AMQP as being documented by the OASIS AMQP Bindings Mappings TC.
Timothy Bish, one of the committers/PMC members at the Apache ActiveMQ
project, is going to join me working on this effort going forward.
Tim has previously done a lot of work on an JMS 1.1 AMQP 1.0 client using
Proton for AMQP 1.0 support, with his existing code being available at
https://github.com/tabish121/NeutronJMS/tree/amqp-only. The code base is
markedly further along in terms of the wider client such as
Connection/Session/Producers/Consumers when compared to the existing work
here at Qpid, which has concentrated initially more on message
implementation and mapping.
We envisage merging our existing work to arrive at the best of both, and
would like to begin doing so within the Qpid project by adding all the
existing code to http://svn.apache.org/viewvc/qpid/jms/trunk/ and then
going forward from there to merge the pieces and work toward tidying things
up and completing remaining areas. Those looking around the code on Github
may spot its previous prototype multi-protocol support; we are only
intending AMQP 1.0 protocol support going forward. Everything is under the
Apache Licence v2, and Tim obviously has an ICLA from his ActiveMQ
participation.
We may also want to think about using Git for our SCM for the JMS work, as
it is a distinct tree and would likely make life easier for collaborating
so extensively with a non-committer.
I just wanted to give a heads up on our thinking and solicit opinion on the
matter before doing anything. Thoughts?
Regards,
Robbie