Is there interest in a second RabbitMQ component/consumer/endpoint?

I found the RabbitMQ support shipped in 2.12 to be pretty sub-par for a bunch of reasons: - host/port must be configured in the URI - vhost must be configured in the URI - autoDelete cannot be specified separately for the Exchange/Queue - durability cannot be specified separately for t

Re: Is there a way to send a message when I am terminating?

I've run up against this before and came accross this https://bugs.eclipse.org/bugs/show_bug.cgi?id=38016 Alex Sherwin alex.sher...@acadiasoft.com > On Nov 8, 2013, at 12:26 PM, "pmp.martins" > wrote: > > Hey there, I found out what the problem was... and I am not

RabbitMQ producer routing key only as an Exchange header?

The code and docs seem pretty clear.. The consumer side makes sense, being able to set the Routing Key for binding and optional Queue name... But why must the producer side set an Exchange header to set the routing key? Doesn't this make it very difficult to write fluent routes.. for example, wi

Transactional test assertions timing issue

When unit (integration) testing a transacted route, such as (pseudo): Where "someBeanProcessor" does some DB work and participates in a JTA transaction with the JMS message on this route The problem is, what is a reliable way to apply an assertion on the work that "someBeanProcessor"