Return-Path: Delivered-To: apmail-activemq-camel-user-archive@locus.apache.org Received: (qmail 80810 invoked from network); 28 Jun 2008 07:33:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Jun 2008 07:33:20 -0000 Received: (qmail 96586 invoked by uid 500); 28 Jun 2008 07:33:21 -0000 Delivered-To: apmail-activemq-camel-user-archive@activemq.apache.org Received: (qmail 96567 invoked by uid 500); 28 Jun 2008 07:33:21 -0000 Mailing-List: contact camel-user-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: camel-user@activemq.apache.org Delivered-To: mailing list camel-user@activemq.apache.org Received: (qmail 96554 invoked by uid 99); 28 Jun 2008 07:33:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 28 Jun 2008 00:33:21 -0700 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [195.69.129.177] (HELO exsmtp01.exserver.dk) (195.69.129.177) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 28 Jun 2008 07:32:28 +0000 Received: from EXVS04.exserver.dk ([10.10.10.85]) by exsmtp01.exserver.dk with Microsoft SMTPSVC(6.0.3790.1830); Sat, 28 Jun 2008 09:31:05 +0200 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: Problem with sending a message from one JMS queue to another Date: Sat, 28 Jun 2008 09:31:05 +0200 Message-ID: <4C1FB9C00D24A140906239533638C4D2049DDDC6@EXVS04.exserver.dk> In-Reply-To: <18069875.post@talk.nabble.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Problem with sending a message from one JMS queue to another Thread-Index: AcjVOT8kSY+JDBE0R+6I01uj4wgWAQzpsW0g From: "Claus Ibsen" To: X-OriginalArrivalTime: 28 Jun 2008 07:31:05.0184 (UTC) FILETIME=[EC835600:01C8D8F0] X-Virus-Checked: Checked by ClamAV on apache.org Hi Bruce Could you create a ticket in JIRA with this issue? So we do not forget = to look into it. Med venlig hilsen =20 Claus Ibsen ...................................... Silverbullet Skovsg=E5rdsv=E6nget 21 8362 H=F8rning Tlf. +45 2962 7576 Web: www.silverbullet.dk -----Original Message----- From: Bruce Elmore [mailto:belmore@qualcomm.com]=20 Sent: 23. juni 2008 16:00 To: camel-user@activemq.apache.org Subject: Problem with sending a message from one JMS queue to another I noticed a problem in JmsBinding.java. If Camel has read a JMS message = from a queue and that message has a bean method specified in the header ("org.apache.camel.MethodName"), the method header will removed if that message is written to another queue. Here's the offending code: protected boolean shouldOutputHeader(org.apache.camel.Message camelMessage, String headerName, Object headerValue) { return headerValue !=3D null && !getIgnoreJmsHeaders().contains(headerName) && ObjectHelper.isJavaIdentifier(headerName); } "org.apache.camel.MethodName" fails the check isJavaIdentifier and is excluded from the headers written to the new message. I'm not sure the purpose of this check, but this might be an unintended side effect. The call chain is something like this: JmsProducer.process JmsBinding.makeJmsMessage JmsBinding.appendJmsProperties JmsBinding.shouldOutputHeader --=20 View this message in context: = http://www.nabble.com/Problem-with-sending-a-message-from-one-JMS-queue-t= o-another-tp18069875s22882p18069875.html Sent from the Camel - Users mailing list archive at Nabble.com.