Return-Path: Delivered-To: apmail-activemq-camel-dev-archive@locus.apache.org Received: (qmail 57414 invoked from network); 19 Jul 2008 10:23:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Jul 2008 10:23:27 -0000 Received: (qmail 74860 invoked by uid 500); 19 Jul 2008 10:23:26 -0000 Delivered-To: apmail-activemq-camel-dev-archive@activemq.apache.org Received: (qmail 74842 invoked by uid 500); 19 Jul 2008 10:23:26 -0000 Mailing-List: contact camel-dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: camel-dev@activemq.apache.org Delivered-To: mailing list camel-dev@activemq.apache.org Received: (qmail 74831 invoked by uid 99); 19 Jul 2008 10:23:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 19 Jul 2008 03:23:26 -0700 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 19 Jul 2008 10:22:31 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1KK9aZ-0007W6-Cg for camel-dev@activemq.apache.org; Sat, 19 Jul 2008 03:22:55 -0700 Message-ID: <18543237.post@talk.nabble.com> Date: Sat, 19 Jul 2008 03:22:55 -0700 (PDT) From: pratibhaG To: camel-dev@activemq.apache.org Subject: RE: How to route using java DSL? In-Reply-To: <4C1FB9C00D24A140906239533638C4D204DB9FAD@EXVS04.exserver.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: pratibha.ghogale@in2m.com References: <18528825.post@talk.nabble.com> <18543123.post@talk.nabble.com> <4C1FB9C00D24A140906239533638C4D204DB9FAD@EXVS04.exserver.dk> X-Virus-Checked: Checked by ClamAV on apache.org You are correct. But jbi:service:http://servicemix.in2m.com/operations/updateprofile/ResolvedErrorService is a jms provider service which puts a message on queue named error.queue and jbi:service:http://servicemix.in2m.com/operations/updateprofile/ResolvedErrorConsumerService is a jms consumer service which consumes a message from same queue that is error.queue. There is no problem with ResolvedErrorConsumerService for consuming the message. I have seen on the logs that It consumes it, only it is not sending it ahead. partibha -- View this message in context: http://www.nabble.com/How-to-route-using-java-DSL--tp18528825s22882p18543237.html Sent from the Camel - Development mailing list archive at Nabble.com.