The way it worked for me was to check for a change in the data before I tried to do anything else during a request.
Then I loaded or modified previously loaded data, then committed. Are you sure you need to check for external changes in the middle of making internal changes? On Wed, Jun 12, 2013 at 4:49 AM, Markus Reich <[email protected]> wrote: > Hi, > > as I mentioned in a post before, I have a process where data is changed > from external. So I realized the solution from Mike where I made a table > with a single field for the timestamp when the data was changed externally. > Now I have a problem :-( > When the data get's invalidated, it's not possible to commit changes, no > exception is thrown just data is rolled back :-( > > You can simulate this, when you > * create a context > * load data > * make change to the data > * invalidate all data in context > * commit changes > > is there a way of this dilemma? It's driving me nuts :-( > > Meex > <[email protected]>
