What I would do is have a queue that triggers a HTTP fetch. The message on
this queue contains the pagination info, eg the start and limit. After each
request, it can then put another message back on the queue with updated
pagination info if there is more left to process. The initial quartz job
can put the "start" message onto the queue to begin the process. This queue
doesn't need to be anything fancy, it could just be a seda
http://camel.apache.org/seda.html
On Sun, Jul 8, 2012 at 2:40 PM, Bob Jolliffe <bobjolli...@gmail.com> wrote:
> I've got a problem which I can't quite figure out how to solve. I
> want to configure a route which fetches xml data (representing health
> facilities) from a repository using a REST http get, transform the
> data and load into another system. Typically triggered from a quartz
> endpoint running every 24 hours.
>
> I have found that this is quite straightforward using quartz, http and
> xslt components. But ... the data coming from the repository is
> paginated so I can't fetch it in a single request.
>
> Is there anyway to create a route in camel DSL (xml or java) which
> makes a series of requests to the http service, incrementing an http
> parameter eg. Page=xx, until some test condition is true in the xml
> result eg. count('/Facilities/Facility')=0
>
> Thanks for any pointers.
>
> Regards
> Bob
>
--
-Sam
