Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 12573 invoked from network); 10 Sep 2008 10:33:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Sep 2008 10:33:08 -0000 Received: (qmail 98608 invoked by uid 500); 10 Sep 2008 10:33:05 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 97829 invoked by uid 500); 10 Sep 2008 10:33:02 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 97818 invoked by uid 99); 10 Sep 2008 10:33:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Sep 2008 03:33:02 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Sep 2008 10:32:12 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 70640234C1D7 for ; Wed, 10 Sep 2008 03:32:44 -0700 (PDT) Message-ID: <1226831346.1221042764458.JavaMail.jira@brutus> Date: Wed, 10 Sep 2008 03:32:44 -0700 (PDT) From: "Cathal Callaghan (JIRA)" To: axis-dev@ws.apache.org Subject: [jira] Updated: (AXIS2-4025) Using JMSMessageID as correlationID for JMS messages In-Reply-To: <1121015943.1221042646446.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/AXIS2-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cathal Callaghan updated AXIS2-4025: ------------------------------------ Attachment: JMSMessageReceiver.java Attaching propsed solution as stated in description > Using JMSMessageID as correlationID for JMS messages > ---------------------------------------------------- > > Key: AXIS2-4025 > URL: https://issues.apache.org/jira/browse/AXIS2-4025 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: kernel, transports > Environment: OS: Windows XP Pro 2002 Service Pack 2 > Reporter: Cathal Callaghan > Fix For: 1.4 > > Attachments: JMSMessageReceiver.java, JMSSender.java > > > The correlationID solution currently in place in Axis2 version 1.4 does not work. > Currently the option is available to specify a correlationID but when the MessageConsumer is created no MessageSelector is specified. This means that the MessageConsumer will take any message off the queue. > Also, currently the only way to use a correlationID is to explicity specify an ID via the JMSConstants.JMS_COORELATION_ID property. This is very restrictive for those who wish to use the option of using the JMSMessageID of the message as the correlationID. > I have attached a proposed solution which firstly ensures that the MessageConsumer is created using a MessageSelector. Also i have given the user a choice, if they explicity specify a correlationID then this will be used otherwise the JMSMessageID of the message will be used as the correlationID. > Thanks, > Cathal -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org For additional commands, e-mail: axis-dev-help@ws.apache.org