Return-Path: X-Original-To: apmail-camel-users-archive@www.apache.org Delivered-To: apmail-camel-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 990CD11DC2 for ; Tue, 3 Jun 2014 12:18:26 +0000 (UTC) Received: (qmail 65989 invoked by uid 500); 3 Jun 2014 12:18:26 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 65942 invoked by uid 500); 3 Jun 2014 12:18:26 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 65931 invoked by uid 99); 3 Jun 2014 12:18:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jun 2014 12:18:26 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of darth.minhster@gmail.com designates 209.85.160.49 as permitted sender) Received: from [209.85.160.49] (HELO mail-pb0-f49.google.com) (209.85.160.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jun 2014 12:18:20 +0000 Received: by mail-pb0-f49.google.com with SMTP id jt11so5425837pbb.36 for ; Tue, 03 Jun 2014 05:18:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=lAc+/o3BVCidia1RPJkvb44bvMKcK86Az+EJ2NYjPRk=; b=U+LTD9HjlYTnxkAuz7q8wKJX+93e25O89V+qcKZYPz1Bit7ghS5XHtmsdJ6QEVEchj sV7qNAPQsVcqVshWR/uIf9yeVIQBoRTMXM6+ZZg+tutNTC8fMPTG/iTljMLtTIaBomF8 WAmEjN+OQWTy8IuZmDWgNQzYyXdOJhY627V4vgs4I8nEjeEGkVQGNEm06/3iC27++z2R 7WWQ8P+5F3Vf4XUwvKKYla6VDazdntQJoNzrP/YurAiV4P+AJuJc2fZbs/jRttombkS0 0yQDoBtNXCe4rGZP8pf0JleO4hFuaKAg1aJW7+ivHC6aJ797cGT1GioyVnntrVjBn3oz +VZw== X-Received: by 10.68.201.68 with SMTP id jy4mr50015341pbc.64.1401797880660; Tue, 03 Jun 2014 05:18:00 -0700 (PDT) Received: from 2001-44b8-3104-c500-3472-f01a-e608-3c34.static.ipv6.internode.on.net (2001-44b8-3104-c500-3472-f01a-e608-3c34.static.ipv6.internode.on.net. [2001:44b8:3104:c500:3472:f01a:e608:3c34]) by mx.google.com with ESMTPSA id ox3sm27409390pbb.88.2014.06.03.05.17.59 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 03 Jun 2014 05:18:00 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: Property values scope in topic route From: Minh Tran In-Reply-To: Date: Tue, 3 Jun 2014 22:17:56 +1000 Content-Transfer-Encoding: quoted-printable Message-Id: <8113A241-FC16-40DD-BB0D-7E044481DC18@gmail.com> References: To: users@camel.apache.org X-Mailer: Apple Mail (2.1510) X-Virus-Checked: Checked by ClamAV on apache.org Hi That's because the camel property doesn't actually get put onto a JMS = message property. I know this sounds confusing but the camel property = does not match JMS message properties. Try and put it on a camel header = instead, The reason why a direct call to route 3 works is because it's run under = the same route execution so the property gets propagated across but it = doesn't survive the JMS trip because camel properties don't get = propagated there. Hope that makes sense. On 02/06/2014, at 11:41 PM, Happy User = wrote: > I wonder if anyone could help me with this. >=20 > 1. Setting Xpath value in a property in route 1 > 2. Setting a body and placing in Topic in route 1 > 3. Reading the value from Topic in route 2 > 4. Am trying to print the property set in Step 1 but am getting null > 5. Calling another route 3 from route 2 > 6. Printing the property set in Step 1 but again null. >=20 > If I call the route 3 from route 1 instead of route 2, am getting the = value > when I print the property. But I want to call route 3 only after route = 2 > completes as I want to process the value from Topic in route 3. >=20 > What is missing here?