> Can we use the JMS transport to talk with brokers like RabbitMQ which are > not written in Java?
AMQP protocol is a language and platform independent protocol. The Qpid JMS client is an AMQP client that implements the JMS interfaces. The Qpid JMS client works well with the Java and C++ brokers in Qpid. It will also work reasonably well with the RabbitMQ broker written in Erlang if the Qpid client has the strict AMQP flag set The Qpid JMS client could work with the OpenMQBroker, all though the OpenMQ broker does not support certain protocol features. The AMQP protocol had significant changes btw 0-8, 0-9. 0-10 and now 1.0 (in progress). And different vendors implemented different versions of the protocol. So interop is not all that great. However the Qpid JMS client implements all 3 versions (0-8/9/10) of the protocol, but there are still some quirks w.r.t vendor interoperability. However the situation is gradually improving. With the AMQP 1.0 version I expect the vendors to have a much better story w.r.t interoperability. > Do you mean to say that we can already use the Axis2 > JMS transport to connect with JMS unaware AMQP brokers? Yes provided that you use a JMS client (not just Qpid) that speaks AMQP. None of the brokers in Qpid is JMS aware. They only speak AMQP. JMS is only a client side API, but does defines some behaviour as well. Note: You also need to take into account the AMQP versions supported by clients and brokers as well. Have I answered your questions clearly? If not please feel free to continue asking questions until you are satisfied. Regards, Rajith --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
