- I don't believe we've revisted AMQP since it hit 1.0 as we've been busy with other things. Hopefully we can take another look soon and prioritize it appropriately. In the mean-time, can you elaborate on your use-case for AMQP? I assume you plan to interact with other AMQP brokers. Is that true? It's always good to have concrete use-cases when trying to prioritize new features.
- The JMS 2.0 spec is still in early draft so we've not implemented anything for it yet.
- I don't believe there is any support for transactions on any level in HornetQ REST.
I don't have a particular use case for AMQP. I'm looking for options for communication - AMQP is one, but also STOMP, and since STOMP is supported, I'll start with it.
I'm interested in using amqp, not to interact with other brokers but to use amqp clients in different languages all talk to each other. I realize STOMP can provide this, and we're currently using STOMP to send messages from php and consume via the JMS api. However, we're starting to see a number of tools we'd like to use/integrate provide hooks to consume messages via amqp, and we either need to switch off of hornetq, bridge hornetq to another amqp broker, or not use these other tools. I'd prefer to stick with hornetq, but be able to use amqp.