Return-Path: 
 <users-return-32819-apmail-camel-users-archive=camel.apache.org@camel.apache.org>
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 A3949D4CE
	for <apmail-camel-users-archive@www.apache.org>;
 Mon, 24 Sep 2012 08:46:49 +0000 (UTC)
Received: (qmail 90979 invoked by uid 500); 24 Sep 2012 08:46:49 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 90643 invoked by uid 500); 24 Sep 2012 08:46:45 -0000
Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@camel.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@camel.apache.org>
List-Post: <mailto:users@camel.apache.org>
List-Id: <users.camel.apache.org>
Reply-To: users@camel.apache.org
Delivered-To: mailing list users@camel.apache.org
Received: (qmail 90595 invoked by uid 99); 24 Sep 2012 08:46:44 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Sep 2012 08:46:44 +0000
X-ASF-Spam-Status: No, hits=2.5 required=5.0
	tests=FREEMAIL_ENVFROM_END_DIGIT,SPF_SOFTFAIL,URI_HEX
X-Spam-Check-By: apache.org
Received-SPF: softfail (nike.apache.org: transitioning domain of
 bhtan1982@live.com does not designate 216.139.236.26 as permitted sender)
Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Sep 2012 08:46:37 +0000
Received: from [192.168.236.26] (helo=sam.nabble.com)
	by sam.nabble.com with esmtp (Exim 4.72)
	(envelope-from <bhtan1982@live.com>)
	id 1TG4Iy-0005yt-M4
	for users@camel.apache.org; Mon, 24 Sep 2012 01:46:16 -0700
Date: Mon, 24 Sep 2012 01:46:16 -0700 (PDT)
From: zuff <bhtan1982@live.com>
To: users@camel.apache.org
Message-ID: <1348476376677-5719834.post@n5.nabble.com>
In-Reply-To: 
 <CAGB5yNnQdncF=9ksSQiKzAE0yuHVD_ObjX7duEpiTN+7ASGNNw@mail.gmail.com>
References: <1348221034371-5719716.post@n5.nabble.com>
 <1348451013762-5719818.post@n5.nabble.com>
 <CAGB5yNnQdncF=9ksSQiKzAE0yuHVD_ObjX7duEpiTN+7ASGNNw@mail.gmail.com>
Subject: Re: Correct use of camelproxy + (Updating Exchange in Spring DSL)?
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi Claus,

   Thanks. That resolved my problem. I didn't even try such a simple
changes, as I thought I had to introduce the camel FactoryBean into my POJO.  


   I have another issue:
Even though I found some similar post regarding storing of variable for
later usage, but most of them are in java DSL which I didnt managed to apply
directly.

   <route>
         <from uri="direct:processResult"/>
         <bean ref="convertor"/>             
         <bean ref="strategyManager"  method="isStrategyCompleted"/>    
         <when>   
                 <simple>${body}</simple>
                 
                 <bean ref="messageSender" />
         </when>
         <otherwise>
           ....
          </otherwise>
   </route>
  

Will appreciated any advise.

Best Regards,
Zuff



--
View this message in context: http://camel.465427.n5.nabble.com/Correct-use-of-camelproxy-tp5719716p5719834.html
Sent from the Camel - Users mailing list archive at Nabble.com.