From users-return-1765-apmail-qpid-users-archive=qpid.apache.org@qpid.apache.org Fri Aug 14 12:39:02 2009 Return-Path: Delivered-To: apmail-qpid-users-archive@www.apache.org Received: (qmail 38553 invoked from network); 14 Aug 2009 12:39:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 14 Aug 2009 12:39:02 -0000 Received: (qmail 87641 invoked by uid 500); 14 Aug 2009 12:39:09 -0000 Delivered-To: apmail-qpid-users-archive@qpid.apache.org Received: (qmail 87592 invoked by uid 500); 14 Aug 2009 12:39:09 -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 87582 invoked by uid 99); 14 Aug 2009 12:39:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Aug 2009 12:39:08 +0000 X-ASF-Spam-Status: No, hits=3.4 required=10.0 tests=HTML_MESSAGE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: 66.196.96.92 is neither permitted nor denied by domain of textux@bellsouth.net) Received: from [66.196.96.92] (HELO smtp119.sbc.mail.re3.yahoo.com) (66.196.96.92) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 14 Aug 2009 12:38:59 +0000 Received: (qmail 13124 invoked from network); 14 Aug 2009 12:38:38 -0000 Received: from unknown (HELO maverick.brjzm.com) (textux@74.177.75.14 with plain) by smtp119.sbc.mail.re3.yahoo.com with SMTP; 14 Aug 2009 12:38:38 -0000 X-YMail-OSG: UE5BFpAVM1my8dfq_yyiIV2fAv_KnzYKYFw_Fq5cvYUKnTCvOoQeNo9wis3qFenILcdOyLP0e1vl4BEhx1rVxq16QvVq09f1q5NcoHkJrHXfRaOcE_pK_IjiZdbpbtlWwUQEAjhq.E4Sq61._zIrul28S9HP8gi0rqAtAeB6._qNA6N_FqUlsxTXhF48Em8Sgzgw_1JstMbXtnmPtNA7ZvxZCJCzdBlrOLDfL_3MiF2.m4bUA9i.JGA08usnabWYndbDdPq24L5E.1MHIwjrsmhbAENNU3TZK1gudmjQELfQmDi4 X-Yahoo-Newman-Property: ymail-3 Message-ID: <4A855ACD.1040503@bellsouth.net> Date: Fri, 14 Aug 2009 08:38:37 -0400 From: Bill Whiting User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b3pre) Gecko/20090513 Fedora/3.0-2.3.beta2.fc11 Thunderbird/3.0b2 MIME-Version: 1.0 To: users@qpid.apache.org Subject: Re: get message by correlationId References: <4A8481D0.5050004@bellsouth.net> In-Reply-To: Content-Type: multipart/alternative; boundary="------------040704060300000004030504" X-Virus-Checked: Checked by ClamAV on apache.org --------------040704060300000004030504 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Thanks for the quick reply Marnie, My application is written in C++, so I don't think that helps. //Bill On 08/14/2009 05:15 AM, Marnie McCormack wrote: > Hi Bill, > > The Java Broker/Client support JMSCorrelationId& JMSMessageId. They > are exposed as part of the properties on the JMSMessage, allowing bridging > across applications and messaging services. > > In the Java example package, the simple.reqresp classes contain code showing > how to get/set the JMSCorrelationId. > > We also support JMSMessageId, and though there are not any examples I can > spot - the logic is the same i.e. the getter/setter is exposed on the > JMSMessage object. This property is set after send or carried across for > non-Qpid messages. > The JMX management interfaces supported in the Java Broker allow a user > to view message content using using the Qpid message Id (which will be the > same as JMSMessageId after send for Qpid messages). > > Hth - give us a shout with any more questions and we'll try to help, > Marnie > On Thu, Aug 13, 2009 at 10:12 PM, Bill Whiting wrote: > > >> Is there a sample program or documentation that shows getting a message >> from a queue by the correlationId or messageId? >> >> //Bill >> >> --------------------------------------------------------------------- >> Apache Qpid - AMQP Messaging Implementation >> Project: http://qpid.apache.org >> Use/Interact: mailto:users-subscribe@qpid.apache.org >> >> >> > > --------------040704060300000004030504--