Return-Path: Delivered-To: apmail-camel-dev-archive@www.apache.org Received: (qmail 63722 invoked from network); 18 May 2009 16:26:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 18 May 2009 16:26:12 -0000 Received: (qmail 56719 invoked by uid 500); 18 May 2009 16:26:12 -0000 Delivered-To: apmail-camel-dev-archive@camel.apache.org Received: (qmail 56687 invoked by uid 500); 18 May 2009 16:26:12 -0000 Mailing-List: contact dev-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list dev@camel.apache.org Received: (qmail 56677 invoked by uid 500); 18 May 2009 16:26:12 -0000 Delivered-To: apmail-activemq-camel-dev@activemq.apache.org Received: (qmail 56674 invoked by uid 99); 18 May 2009 16:26:12 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 May 2009 16:26:12 +0000 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; Mon, 18 May 2009 16:26:10 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 928DC234C004 for ; Mon, 18 May 2009 09:25:50 -0700 (PDT) Message-ID: <1848841080.1242663950584.JavaMail.jira@brutus> Date: Mon, 18 May 2009 09:25:50 -0700 (PDT) From: "Edward Campbell (JIRA)" To: camel-dev@activemq.apache.org Subject: [jira] Updated: (CAMEL-1624) Subject not correctly set in xmpp message in both chat producers. In-Reply-To: <687488526.1242663590576.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: ae95407df07c98740808b2ef9da0087c X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/activemq/browse/CAMEL-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Campbell updated CAMEL-1624: ----------------------------------- Description: The code in XmppPrivateChatProducer and XmppGroupChatProducer does not call setSubject() on the org.jivesoftware.smack.packet.Message object. Setting a subject property on the org.apache.camel.Message object produces a header on the Smack object via its superclass org.jivesoftware.smack.packet.Packet, but that never gets reflected in the Message object because the Message object does not override the setProperty() method on Packet. private void send(String camelConnectionString) { final CamelContext camel = new DefaultCamelContext(); camel.start(); Endpoint endpoint = camel.getEndpoint(camelConnectionString); Exchange exchange = endpoint.createExchange(ExchangePattern.InOut); Producer producer = endpoint.createProducer(); producer.start(); // send the message Message message = exchange.getIn(); message.setBody("The message body"); message.setHeader("subject", "Message subject for filtering."); producer.process(exchange); } The annoying part about this, is that I am trying to integrate with a receiving system that handles messages using the subject as a key to determine how the message should be handled. was: The code in XmppPrivateChatProducer and XmppGroupChatProducer does not call setSubject() on the org.jivesoftware.smack.packet.Message object. Setting a subject property on the org.apache.camel.Message object produces a header on the Smack object via its superclass org.jivesoftware.smack.packet.Packet, but that never gets reflected in the Message object because the Message object does not override the setProperty() method on Packet. private void send(String camelConnectionString) { final CamelContext camel = new DefaultCamelContext(); camel.start(); Endpoint endpoint = camel.getEndpoint(camelConnectionString); Exchange exchange = endpoint.createExchange(ExchangePattern.InOut); Producer producer = endpoint.createProducer(); producer.start(); // send the message Message message = exchange.getIn(); message.setBody("The message body"); message.setHeader("subject", "Message subject for filtering."); producer.process(exchange); } The annoying part about this, is that I am trying to integrate with a receiving system that handles messages based using the subject as a key to determine how the message should be handled. > Subject not correctly set in xmpp message in both chat producers. > ----------------------------------------------------------------- > > Key: CAMEL-1624 > URL: https://issues.apache.org/activemq/browse/CAMEL-1624 > Project: Apache Camel > Issue Type: Bug > Components: camel-xmpp > Affects Versions: 1.6.1 > Reporter: Edward Campbell > > The code in XmppPrivateChatProducer and XmppGroupChatProducer does not call setSubject() on the org.jivesoftware.smack.packet.Message object. > Setting a subject property on the org.apache.camel.Message object produces a header on the Smack object via its superclass org.jivesoftware.smack.packet.Packet, but that never gets reflected in the Message object because the Message object does not override the setProperty() method on Packet. > private void send(String camelConnectionString) { > final CamelContext camel = new DefaultCamelContext(); > camel.start(); > Endpoint endpoint = camel.getEndpoint(camelConnectionString); > Exchange exchange = endpoint.createExchange(ExchangePattern.InOut); > Producer producer = endpoint.createProducer(); > producer.start(); > // send the message > Message message = exchange.getIn(); > message.setBody("The message body"); > message.setHeader("subject", "Message subject for filtering."); > producer.process(exchange); > } > The annoying part about this, is that I am trying to integrate with a receiving system that handles messages using the subject as a key to determine how the message should be handled. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.