I refer to this JIRA issue, which was submitted back in June 2011 and on which there was a lively debate involving
various EG members.
> http://java.net/jira/browse/JMS_SPEC-9 Support for AMQP messaging
>
> AMQP adds support for a number of the same things that JMS supports today, and adds to that model I believe that by
> JMS 2.0 supporting the AMQP model it allows for cross-system integration, as well as cross-language integration.
(I note that additional AMQP experts have joined this EG since then, and there are AMQP experts in the user community as
well).
AMQP is a wire protocol, and I think there's already a general consensus that JMS should remain as an API and shouldn't
define a wire protocol.
However AMQP is clearly a prominent and successful standard and it's definitely within the scope of JMS to consider
whether new JMS features would make it easier for vendors to implement JMS providers that use AMQP as a wire protocol.
I think what we need to take this issue forward is some concrete proposals as to what this might involve. Without
specific proposals this will remain just an expression of desire.
So please take this as an invitation to make some proposals. Depending on the scale of changes proposed, these could be
for JMS 2.0 or a later revision.
(If you'd like to make some proposals, but don't have the time to do so right now, an expression of future intent would
be helpful.)
Nigel