Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.215.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAPkuR4M3_YaLeY46LRoQOBPL8560oWUTesf4eoZ4xWF48j17sA@mail.gmail.com>
References: 
 <CAPkuR4M3_YaLeY46LRoQOBPL8560oWUTesf4eoZ4xWF48j17sA@mail.gmail.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Wed, 15 Aug 2012 15:00:29 +0200
Message-ID: 
 <CAGB5yNkwXHJQZS_Dh790CBNr6brVXuiOd1SdD-iy3hokwyE=0A@mail.gmail.com>
Subject: Re: enrich and pollEnrich
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Aug 15, 2012 at 2:53 PM, Joe San <codeintheopen@gmail.com> wrote:
> Camel Riders,
>
> I fail to fathom the fact that enrich works with a Producer EndPoint and
> pollEnrich works with a Consumer EndPoint. Is there a design consideration
> behind this mechanism? Can anyone please clarify why a pollEnrich should be
> used with a Consumer EndPoint and not with a Producer EndPoint? Has it got
> something to do with the Message type (request only or request / response)?
>

Yes some components support both producers and consumers, and behave
differently.
For example file/ftp components. The producer will write a file, and
the consumer read a file.

Where as a http component may only support the producer, etc.


> Regards,
> Jothi


-- 
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen