camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: Database polling and persisting properties
Date Fri, 18 Sep 2015 07:08:48 GMT
That is something you would need to implement.

Or maybe if possible design the solution so you can update a column or
something in the database when you have processed the data so you do
not need to rely on timestamps and state to know where "you were".

On Fri, Sep 18, 2015 at 1:14 AM, Cleocleo <sethduda@gmail.com> wrote:
> Any best practices for persisting properties (which can change at runtime)
> between jvm restarts?
>
> For example, let's say I have a polling consumer that queries a db for all
> records which have been updated since the last time the route executed. If I
> were to restart the jvm + route, how do I persist this last run date so it's
> used when the route starts back up?
>
> I'm running camel w/in a web app on tomcat.
>
> Is this something that I would need to implement (e.g. store/read persisted
> property in a shared db before and after querying the database) or is there
> any out of the box functionality I can take advantage of?
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Database-polling-and-persisting-properties-tp5771609.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2nd edition:
https://www.manning.com/books/camel-in-action-second-edition

Mime
View raw message