Wow, I didn’t know this was possible. Nice trick.
Still the poll consumer seems to be the most intuitive choice if you come from
EIP mindset. I never thought of my route as doing a data transformation, but
rather a content enrichment. Anyway, I wonder if others will be hit by the
same problem where it does not work correctly when used under high concurrency.
Thank you Claus.
Best regards,
Alex soto
> On Aug 18, 2016, at 2:12 AM, Claus Ibsen <claus.ib...@gmail.com> wrote:
>
> Its easier to do a message transformation and set the body as a java.io.File
>
> <transform>
> <simple type="java.io.File">{{env:HOME}}/my-dir/${body}</simple>
> </transform>
>
>
> On Tue, Aug 16, 2016 at 8:39 PM, Alex Soto <alex.s...@envieta.com> wrote:
>> Hello,
>>
>> I am experiencing erratic results when using the Poll Enrich with a static
>> file.
>> The file is static in the sense that it never changes, so I am setting both
>> the noop=true and the idempotent=false.
>> Basically I need to be able to serve this same files for ever, and not move
>> it or deleted it.
>>
>> My route sets the body with the file name, then it continues with:
>>
>> <pollEnrich timeout="5000">
>>
>> <simple>file:{{env:HOME}}/my-dir?noop=true&fileName=${body}&idempotent=false</simple>
>> </pollEnrich>
>>
>> It works a few times, but after this is executed several times (from
>> multiple clients concurrently), the body becomes null, even though, the file
>> is still present in the directory.
>> Am I setting the options correctly? How can this be accomplished?
>>
>> Best regards,
>> Alex soto
>>
>>
>>
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
