Well put. Could we use active MQ on both sides? Plus if we did, we would not need to build a broker with camel.
Sent using my iPhone > On Dec 20, 2013, at 1:00 PM, uromahn <[email protected]> wrote: > > I have a general question to this community, especially to the active project > committers: > > I was wondering what the status of the amqp-1-0-* libraries is and if this > is even still actively maintained? > > I was planning to use the AMQP-1-0- JMS client library in my project here > and started testing it out with a very simple proof-of-concept. > However, even the very first steps were very discouraging since I > encountered some serious bugs and very strange behavior (see Jira tickets > QPID-5348 and QPID-5349 as two examples). In addition, the client does not > yet fully implement the complete JMS 1.1 spec (e.g. no XA support), and > there seems to be some subtle deviations from the spec in some areas. > Also, when looking at the current code, I don't really get a good "warm and > fuzzy" feeling since the code quality seems very questionable in many places > (sorry for being so brutally honest here, but I have very high personal > standards when it comes to Java). > > I also noticed that there is a new project to build a JMS 2.0 client based > on Proton, however, this does not seem to have a lot of traction and > activity and it is far from being close to production readiness. > > So, here is my final question: > should I just abandon the idea to use JMS together with AMQP 1-0 and switch > to ProtonJ (which seems much better :) ) or is there hope that we can get > the existing JMS-AMQP-1-0 client libraries to some level of quality? I am > willing to chip in some of my time, but I don't want to be the "lonely > warrior" here. > > -Uli > > > > -- > View this message in context: > http://qpid.2158936.n2.nabble.com/INQUIRY-Status-of-qpid-java-amqp-1-0-client-jms-library-tp7602075.html > Sent from the Apache Qpid users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
