Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Date: Thu, 8 Nov 2012 03:45:20 -0800 (PST)
From: sushil_vsk5 <sushil_vsk5@yahoo.co.in>
To: users@camel.apache.org
Message-ID: <1352375120458-5722364.post@n5.nabble.com>
In-Reply-To: <1351763496804-5721963.post@n5.nabble.com>
References: <1351699045726-5721888.post@n5.nabble.com>
 <1351704488777-5721901.post@n5.nabble.com>
 <1351743945728-5721926.post@n5.nabble.com>
 <1351763496804-5721963.post@n5.nabble.com>
Subject: Re: Camel Bean Component Behaviour in case of an InOut exchange
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi,
I tasted with the stable release and also by adding a log at the end of my
route. But still I am not getting a response. I am always getting back the
original request on my reply queue. Can you throw any light on this?
Regards,
Sushil


--
View this message in context: http://camel.465427.n5.nabble.com/Camel-Bean-Component-Behaviour-in-case-of-an-InOut-exchange-tp5721888p5722364.html
Sent from the Camel - Users mailing list archive at Nabble.com.