2008/5/28 Robert Greig <[EMAIL PROTECTED]>: > 2008/5/28 TLFox <[EMAIL PROTECTED]>: > >> Ok sorry to be a pain. But there's also an issue with doing acknowledgements >> asynchronously and JMS compliance. >
In general the goal of Qpid is to provide AMQP brokers and clients in a number of different languages, Qpid is explictly not aiming to be a "JMS Broker". However, since the common API for messaging in Java is JMS we have attempted to layer JMS on top of AMQP. Our work in trying to do this on the AMQP0-8/0-9 protocols has led directly to the changes for AMQP0-10. Some of this has involved using Qpid as a testbed for proposals for protocol extensions. I believe that the Java Client/Broker on M2 / M2.1 are probably close enough to the JMS specification that they could pass a TCK; however for all sorts of reasons we do not claim any sort of JMS compliance. The 0-10 protocol is such that (apart from one very small and annoying omission for a particular case of restoring durable subscriptions after a client reconnection) it should be possible to build a 100% compliant JMS implementation without any extensions to the core AMQP protocol. As we progress AMQP I hope that we can remove any remaining such incompatibilities and also publish a standard mapping so that JMS clients from different AMQP vendors will interoperate seamlessly. Hope this helps, Rob
