Return-Path: 
 <users-return-14448-apmail-camel-users-archive=camel.apache.org@camel.apache.org>
Delivered-To: apmail-camel-users-archive@www.apache.org
Received: (qmail 57561 invoked from network); 9 Jul 2010 00:39:48 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 9 Jul 2010 00:39:48 -0000
Received: (qmail 28601 invoked by uid 500); 9 Jul 2010 00:39:47 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 28552 invoked by uid 500); 9 Jul 2010 00:39:47 -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 28544 invoked by uid 99); 9 Jul 2010 00:39:47 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Jul 2010 00:39:47 +0000
X-ASF-Spam-Status: No, hits=2.0 required=10.0
	tests=FREEMAIL_FROM,SPF_HELO_PASS,SPF_NEUTRAL,T_TO_NO_BRKTS_FREEMAIL,URI_HEX
X-Spam-Check-By: apache.org
Received-SPF: neutral (nike.apache.org: 216.139.236.158 is neither permitted
 nor denied by domain of bryanck@gmail.com)
Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Jul 2010 00:39:40 +0000
Received: from sam.nabble.com ([192.168.236.26])
	by kuber.nabble.com with esmtp (Exim 4.63)
	(envelope-from <bryanck@gmail.com>)
	id 1OX1cd-0003rc-RV
	for users@camel.apache.org; Thu, 08 Jul 2010 17:39:19 -0700
Date: Thu, 8 Jul 2010 17:39:19 -0700 (PDT)
From: bryan <bryanck@gmail.com>
To: users@camel.apache.org
Message-ID: <1278635959846-1045274.post@n5.nabble.com>
Subject: Spring remoting proxy call from within a route bean
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org


I was wondering if the following design was acceptable, or if there is a
better way of doing it. Currently I have a route that reads in a CSV, parses
it, and passes it to a bean. Inside the bean's method call, the CSV data is
converted to an object. The bean also has a reference to a camel spring
remoting proxy, and it calls a method on this and passes in the object. The
proxy adds a message to a queue. 

I was concerned that I was calling the proxy from within the bean's route
method. This seems like it will start a new route from within the first
route. It seems to work fine, but wanted to make sure I wouldn't get bitten
by this down the road. 

My route looks like this: 

<camelContext id="camelContext"> 
<proxy id="myProxy" 
  serviceUrl="activemq:queue:myQueue?transferException=true" 
  serviceInterface="com.pkg.MyApi" /> 
<endpoint id="fileInput" uri="file:${my.file.dir}" /> 
<route> 
  <from ref="fileInput" /> 
  <split  parallelProcessing="false" streaming="true"> 
    <tokenize token="\n" regex="false" /> 
    <unmarshal><csv /></unmarshal> 
    <bean ref="inputBean" method="translate" /> 
  </split> 
</route> 
</camelContext> 

The inputBean has a reference to myProxy, and it calls a method on myProxy
inside the translate() method. 
-- 
View this message in context: http://camel.465427.n5.nabble.com/Spring-remoting-proxy-call-from-within-a-route-bean-tp1045274p1045274.html
Sent from the Camel - Users mailing list archive at Nabble.com.