I have the next scenario:
I need to implement something like this:
I have a file.txt with id's
I have splitted those id's by \n and I need to do:
>From file.txt ->
split->
for each id make a GET request on a url (www.example.com). This url
send to me some JSON ->
Unmarshal JSON to xml.
That's all.
My ideas & implementation:
1. route from url to some output (let's say I will put the JSON's in
a folder).
<route autostartup="false">
<from uri="example.com" />
<to: uri="JSONFolder"/>
</route>
2. route from file.txt to seda
<route >
<from uri="file.txt" />
<make a split>
<to: uri="seda:ids"/>
</route>
3. route from seda:ids to myProcessor
<route >
<from uri="seda:ids" />
<processor>
</route>
myProcessor just starts the route from where I GET the JSONs
*The problem is*: I need a JSON for each id. One id will have a JSON file.
But the GET is making requests continuously to the url. And I end with a lot
of JSONs instead of the same nr of JSONs as the number of id's.
*How can I stop the 1st route from making requests continously??*
I tought seda will solve it and the nr of requests will be the same number
as the id's from my file, but I'm wrong somehow.
Thanks, guys!
--
View this message in context:
http://camel.465427.n5.nabble.com/How-to-stop-a-route-from-processing-get-requests-continously-tp5759649.html
Sent from the Camel - Users mailing list archive at Nabble.com.
