Return-Path: 
 <camel-user-return-4149-apmail-activemq-camel-user-archive=activemq.apache.org@activemq.apache.org>
Delivered-To: apmail-activemq-camel-user-archive@locus.apache.org
Received: (qmail 94178 invoked from network); 7 Nov 2008 12:31:53 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 7 Nov 2008 12:31:53 -0000
Received: (qmail 56274 invoked by uid 500); 7 Nov 2008 12:32:00 -0000
Delivered-To: apmail-activemq-camel-user-archive@activemq.apache.org
Received: (qmail 56257 invoked by uid 500); 7 Nov 2008 12:32:00 -0000
Mailing-List: contact camel-user-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:camel-user-help@activemq.apache.org>
List-Unsubscribe: <mailto:camel-user-unsubscribe@activemq.apache.org>
List-Post: <mailto:camel-user@activemq.apache.org>
List-Id: <camel-user.activemq.apache.org>
Reply-To: camel-user@activemq.apache.org
Delivered-To: mailing list camel-user@activemq.apache.org
Received: (qmail 56246 invoked by uid 99); 7 Nov 2008 12:32:00 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Nov 2008 04:32:00 -0800
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; Fri, 07 Nov 2008 12:30:41 +0000
Received: from isper.nabble.com ([192.168.236.156])
	by kuber.nabble.com with esmtp (Exim 4.63)
	(envelope-from <lists@nabble.com>)
	id 1KyQUl-00072x-2u
	for camel-user@activemq.apache.org; Fri, 07 Nov 2008 04:31:23 -0800
Message-ID: <20379735.post@talk.nabble.com>
Date: Fri, 7 Nov 2008 04:31:23 -0800 (PST)
From: GLD <guillaume.lundy@orange-ftgroup.com>
To: camel-user@activemq.apache.org
Subject: RE: How to process the response in Camel
In-Reply-To: <4C1FB9C00D24A140906239533638C4D205EC09E1@EXVS04.exserver.dk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: guillaume.lundy@orange-ftgroup.com
References: <20378039.post@talk.nabble.com>
 <4C1FB9C00D24A140906239533638C4D205EC0991@EXVS04.exserver.dk>
 <20378945.post@talk.nabble.com>
 <4C1FB9C00D24A140906239533638C4D205EC09E1@EXVS04.exserver.dk>
X-Virus-Checked: Checked by ClamAV on apache.org


Please have a look at my previous reply, I've updated it : I added the
exchange format in the endpoint uri.
There are no changes.
  
May be the method ProducerCache.sendExchange() should be modified  : 
    protected E sendExchange(Endpoint<E> endpoint, Producer<E> producer,
Processor processor, E exchange) throws Exception {
        processor.process(exchange);

        // now lets dispatch
        if (LOG.isDebugEnabled()) {
            LOG.debug(">>>> " + endpoint + " " + exchange);
        }

        >>> GLD : <<< GLD : call defined processor chain in the route up to
the <to>  endpoint
        producer.process(exchange);     

       >>> GLD : reply route processing to insert here??????
        return exchange;
   }   


Guillaume


Claus Ibsen wrote:
> 
> Hi
> 
> Ah there might miss a method for the multiple headers, 
> 
> Do you mind creating a ticket in the bug tracker for this issue. Then I
> will make sure it's added.
> 
> There is a link to the tracker from here:
> http://activemq.apache.org/camel/support.html
> 
> 
> 
> 
I'm off this afternoon.
I will do it next week.

-- 
View this message in context: http://www.nabble.com/How-to-process-the-response-in-Camel-tp20378039s22882p20379735.html
Sent from the Camel - Users mailing list archive at Nabble.com.