Roger, Marnie & Rajith ,
Thank you for the responses ... they have clarified a lot. I'm
currently working on a QPid gateway for the JBoss ESB. For the most
part, it is working well. I did experience a couple of issues and I'll
follow this up with a new post that addresses them.
thanks again!
I would use JMS unless there is a feature you need is currently not exposed
via configuration + pure JMS.
My experience is that most use cases could be handled using pure JMS +
configuration via the JNDI file.
There are currently a few limitations such as not being able to bind a queue
to multiple
I'd agree with Robert here, particularly with the upcoming work to implement
AMQP 0-10 and 1-0 on the Java Broker. I'd stick to JMS, unless there's a
feature you need exposed that this won't give you ?
Marnie
On Fri, Jan 30, 2009 at 9:01 PM, Robert Greig wrote:
> 2009/1/30 Jeffrey Bride :
>
> >
2009/1/30 Jeffrey Bride :
> I have the liberty of deciding whether to use a JMS or AMQP flavored
> (via org.apache.qpid.transport.Session) approach in my producers and
> consumers and I'm wondering whether experts on this list might have a
> bias between the two ? In particular, I've been using
Hi,
The U.S. Marine Corps is moving toward a service oriented approach of
developing their software. As such, we've decided to use AMQP as the
wire protocol between services.
Our first stab with AMQP has JBoss ESB gateways and notifiers
communicating with the latest C++ QPid broker. We are us
