This content has been marked as final. Show 4 replies
Did somebody respond to your enquiry? I have the same problem.
We discussed about this issue with Oracle Support. According to the ADF product managers this is not a bug but intended behavior.
That's indeed an intended behaviour.
At the same time we raise the RowInconsistentException, we refresh the state of the Entity Object from the database.
You can override the lock() method to your needs.
I provided an example in Note 842855.1 - RowInconsistentException (JBO-25014) Ignored By Second Commit
available from My Oracle Support, where the second commit will keep raising the JBO-25014 error.
Hope that helps,
Thank you very much for your response. I'll incorporate the changes.