Mailing-List: contact camel-user-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-user@activemq.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <484D9388.8040705@die-schneider.net>
Date: Mon, 09 Jun 2008 22:33:12 +0200
From: Christian Schneider <chris@die-schneider.net>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: camel-user@activemq.apache.org
Subject: Re: from http://... to file://...
References: <4C1FB9C00D24A140906239533638C4D20461C523@EXVS04.exserver.dk>
In-Reply-To: <4C1FB9C00D24A140906239533638C4D20461C523@EXVS04.exserver.dk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

What I still don�t understand. What is the difference between the jetty 
and the http component and why are both needed? Normally I would have 
thought the jetty component hosts a server that can be used to trigger a 
camel route from the outside. But in the example you used it to extract 
data from an external page. Am I missing something here?

Greetings

Christian

Claus Ibsen schrieb:
> Hi
>
> Ah the issue is that the Jetty component is an EventDrivenConsumer and not Scheduled. So you have to trigger the event yourself to start the event in jetty.
>
> Eg:
> from("timer://foo?fixedRate=true&delay=0&period=10000").to("jetty:http://www.google.com").setHeader(FileComponent.HEADER_FILE_NAME, "message.txt").to("file:target/hello");
>
> This will invoke the google homepage every 10th second and store it as a file.
>
> http://activemq.apache.org/camel/event-driven-consumer.html
>
>
> Med venlig hilsen
>  
> Claus Ibsen
>