qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rajith Attapattu <rajit...@gmail.com>
Subject Re: use of JMS or AMQP style clients ??
Date Mon, 02 Feb 2009 21:58:38 GMT
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 exchange/routing key pairs or not being able to specify
arguments when declaring queues/exchanges or when binding queues. However we
are currently working/planning to work on these aspects.

The danger of using something close to the AMQP wire protocol is that there
will be some pain when it changes.
So I would avoid using such an API atleast until there is support for AMQP
1.0 where there will be some guarantee on backwards compatibility.

If you are in doubt about whether your use cases can be met with pure JMS +
configuration please feel free to descibe them in abstract form.
The Qpid developers could help find the solutions within the current
structure or if unable to meet we could make sure we add them to our to do
list.

Regards,

Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/

On Fri, Jan 30, 2009 at 3:44 PM, Jeffrey Bride <jbride@redhat.com> wrote:

> 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 using the QPid
> java client libraries.
>
>  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 the examples
> included in :
>
>
> $QPID_JAVA_SRC/client/examples/src/main/java/org/apache/qpid/example/amqpexample.*
>    and
>
> $QPID_JAVA_SRC/client/examples/src/main/java/org/apache/qpid/example/jmsexample.*
>
> personally, I like using org.apache.qpid.transport.Session to produce &
> consume messages because it seems much more inline with the way the AMQP
> spec describes things.
>
> thoughts ??
>
> thank you !    jeff
>
>
>
>
>
> --
> Jeffrey Bride
> RedHat / JBoss
> 303-523-7885
>
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:users-subscribe@qpid.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message