Thanks for the explanation.
>From your example in the Camel in Action book in Chapter 3:
from("quartz://report?cron=0+0+6+*+*+?")
.to("http://riders.com/orders/cmd=received&date=yesterday";)
.process(new OrderToCsvProcessor())
.to("file://riders/orders?fileName=report-${header.Date}.csv");
Your statement "Where as a http component may only support the producer". I
would understand the above route as follows
>From the quartz Producer to http Consumer, process and send to file
Consumer. Is it interpreted this way? or the role of a component (Producer
or Consumer) depends on the component type?
Regards,
Jothi
On Wed, Aug 15, 2012 at 3:00 PM, Claus Ibsen <claus.ib...@gmail.com> wrote:
> On Wed, Aug 15, 2012 at 2:53 PM, Joe San <codeintheo...@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: cib...@fusesource.com
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
>
