Hi It will poll this in an endless loop, its better to use a timer to schedule how often to call the http service if you want to call it repetitively.
from timer to http On Thu, Jan 29, 2015 at 4:45 AM, Willem Jiang <willem.ji...@gmail.com> wrote: > What kind of warning did you get? > Using the HTTP component as a pulling consuming is OK from my point of view. > It just pulling the result from url with the GET method. > > -- > Willem Jiang > > Red Hat, Inc. > Web: http://www.redhat.com > Blog: http://willemjiang.blogspot.com (English) > http://jnn.iteye.com (Chinese) > Twitter: willemjiang > Weibo: 姜宁willem > > > > On January 29, 2015 at 9:57:29 AM, muell01 (rob.muell...@hp.com) wrote: >> >> I use the following as a REST consumer from an external service. I know the >> warning in the Camel docs... but am I using this a webservice consumer or as >> a Rest Client. >> Is this form proper? If not what would I replace it with? >> Would someone explain what the ramifications are in using HTTP as a >> consumer. (I know the warnings are dire, but why?) >> >> > uri="http://api.application.com/v1/pull?id={{streamId}}&api_key={{api_key}}&username={{username}}"/> >> >> Rob >> >> >> >> -- >> View this message in context: >> http://camel.465427.n5.nabble.com/HTTP-consumer-Terminology-confusing-tp5762190.html >> Sent from the Camel - Users mailing list archive at Nabble.com. >> > -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
