Return-Path: Delivered-To: apmail-qpid-users-archive@www.apache.org Received: (qmail 28418 invoked from network); 20 Aug 2009 07:47:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 20 Aug 2009 07:47:44 -0000 Received: (qmail 89775 invoked by uid 500); 20 Aug 2009 07:48:02 -0000 Delivered-To: apmail-qpid-users-archive@qpid.apache.org Received: (qmail 89736 invoked by uid 500); 20 Aug 2009 07:48:02 -0000 Mailing-List: contact users-help@qpid.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@qpid.apache.org Delivered-To: mailing list users@qpid.apache.org Received: (qmail 89726 invoked by uid 99); 20 Aug 2009 07:48:02 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Aug 2009 07:48:02 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [83.206.112.232] (HELO mailgw1.z-ancy-11.fr.sopragroup.com) (83.206.112.232) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Aug 2009 07:47:52 +0000 Received: from mailgw1.z-ancy-11.fr.sopragroup.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 1BB75D1C0B2 for ; Thu, 20 Aug 2009 09:47:32 +0200 (CEST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: Mixing up AMQP QPID and JMS Date: Thu, 20 Aug 2009 09:47:30 +0200 Message-ID: <3003_1250754452_4A8CFF94_3003_1147468_1_375BF4705DE42C43937DF48DA7E5845CB5CF26@WBE13.ancy.fr.sopra> In-Reply-To: <129a14790908191113k69905d74had0160d9c3f64337@mail.gmail.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Mixing up AMQP QPID and JMS Thread-Index: Acog+MtVN/qi7PMxTGejLBV8RMr/GAAb4Ggg References: <3005_1250684196_4A8BED24_3005_5405967_1_375BF4705DE42C43937DF48DA7E5845CB5CD4F@WBE13.ancy.fr.sopra> <4A8C0803.4090207@redhat.com> <3005_1250694868_4A8C16D4_3005_5420304_1_375BF4705DE42C43937DF48DA7E5845CB5CE70@WBE13.ancy.fr.sopra> <4A8C18B0.1070805@redhat.com> <3005_1250699816_4A8C2A28_3005_5425453_1_375BF4705DE42C43937DF48DA7E5845CB5CEC8@WBE13.ancy.fr.sopra> <129a14790908191113k69905d74had0160d9c3f64337@mail.gmail.com> From: "Leglise Yann" To: X-OriginalArrivalTime: 20 Aug 2009 07:47:30.0010 (UTC) FILETIME=[782F5BA0:01CA216A] X-Virus-Checked: Checked by ClamAV on apache.org Hello Robert, I am not particulary trying to create queues dynamically. I am in fact = trying to determine if by using the JMS QPID implementation leads to an = AMQP compliant behaviour. I mean, by using JMS, as soon as a use a = consumer on an non-existing queue, this queue is automatically created = in the broker. Would this happen if I used "low level" QPID java, or C++ = or python? As we discussed before, QPID is an implementation of AMQP, so I expected = that whichever was the underlying language or library used, the use of = QPID would lead to the same result, i.e. the behaviour specified in = AMQP. As I have read that in AMQP queues should be explicitely declared, I was = just wondering if the automatic queue creation achieved through JMS was = acceptable since it was not the behaviour described by AMQP, or in other = words, I am wondering if the JMS QPID implementation is AMQP compliant. Regards. Yann LEGLISE -----Message d'origine----- De : Robert Greig [mailto:robert.j.greig@gmail.com]=20 Envoy=E9 : mercredi 19 ao=FBt 2009 20:13 =C0 : users@qpid.apache.org Objet : Re: Mixing up AMQP QPID and JMS 2009/8/19 Leglise Yann : > 2) If it is, are both implementations equivalent and compliant with = AMQP the same way? I am asking because using JMS, when you create a = Consumer on a queue that is not declared as an administered object, this = queue is created in the broker. This isn't generally the case, it is dependent on the message broker you = are using. Nearly all brokers will have permissions to limit which = clients can create queues. > I believe this a a normal JMS behaviour, but I have read somewhere = that in AMQP, queues must be explicitly declared, what I understood by = "if queues are not explicitly declared, they cannot be used". This is likely referring to the underlying protocol. Higher level APIs = such as JMS are designed to shield the developer from the low level = details. Are you trying to write an application that requires queues be created = dynamically at run-time by a client? Robert --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:users-subscribe@qpid.apache.org --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:users-subscribe@qpid.apache.org