Monday, March 4, 2013

ADF Rollback Operation and Stay On Current Row

This post is extension for my previous posts about ADF CRUD and is based on - ADF Query Search and Results Form blog. As most likely you have noticed it already, Rollback operation in ADF removed all pending changes plus it resets current row to the first row in data collection. Resetting current row to the first is not always desirable, I will provide sample application which demonstrates how to prevent resetting to first row after Rollback operation was invoked.

Download completed sample application - There are two ADF BC generic classes with overridden methods you should pay attention for in this sample - GenericVOImpl and GenericAMImpl.

GenericVOImpl contains beforeRollback(...) and afterRollback(...) overridden methods. beforeRollback(...) is responsible to retrieve and store current row key and range index (so we can reset it back):

afterRollback(...) method sets current row key back and scrolls to current row range (this allows to preserve current row on the UI with single generic and reusable implementation in ADF BC):

You must override prepareSession(...) method in Application Module generic class and disable clearing cache on rollback (otherwise nothing will help to keep current row, even setting it programmatically):

Let's do a test now - search with ADF Query and scroll few records, we can change hire date value:

Press Cancel button now:

Unsaved data will be cleaned and data row restored to its original state - current row remains the same:


ILya Cyclone said...

Hello Andrejus,
Many thanks for this post. Could you please explain if this method is passivation/activation safe as we're using BC variable?
Any side effects of overriding prepareSession in this way?

Andrejus Baranovskis said...


Yes - it is safe for passivation/activation, I was testing with AM pool disabled, no issues recorded.

I didn't encounter side effects specific to disabling clear cache on rollback at this moment. VO is re-executed from afterRollback method.


Vanessa said...

Hello Andrejus

First of all thanks for this post and many others, are very useful for me.
I have a problem that I think is related to this topic.

I have an af:table with CRUD buttons and popups to modify the data table. When I move the scroll to see the records in the middle of the table and click the edit button to open popup to edit record, when I rollback the operation the vertical scrollbar automatically resets to the top position and the currentRow remains in the correct row. When I do the same but commit the operation, the vertical scrollbar don't moves.

I override the beforeRollback/afterRollback methods as you suggest. I save the getRangeStart return value within the beforeRollback method and tried to set with scrollRange(range) or scrollToRangePage(range) methods within the afterRollback but nothing changes, the scrollbar resets to the top position. The getCurrentRow and getRangeStart methods return the original values before rollback, but the scrollbar continue moving at the top position of the table.

I execute the addPartialTarget method to refresh the af:table. When I comment this method then the scrollbar don't moves, but obviously the changes don't show.

Furthermore, the same application don't moves the scrollbar in JDeveloper, now I'm using JDeveloper

Is there any way to control the position of the scroll? Or is there any way to refresh the table without resetting the scroll?

Any ideas would be appreciated.


Andrejus Baranovskis said...


Approach described here will work only for ADF form component. I know what you mean by keeping selected row in the table after scrolling, I faced this also - it looks to be a bug in latest JDev version, I didnt had time to look for workaround yet.


Emmerson Miranda said...


This code take the state of the current row of viewObject, that works fine when -Djbo.ampool.doampooling=false.

But when is true, the better option is take the current state of the entities associates of current row, if the VO is based on entities.

You can prove this creating a row master, doing commit, create a row child in the last row create and make rollback while editing the detail row, then you can watch how current row is moved to another row master.

Andrejus Baranovskis said...


Yes indeed - this sample app is using row state from VO, mainly because of the issues related to Entity cache, when several VO instances using same EO - we had issues.

But generally I agree, is good to use state from EO - depends on the use case.


Anonymous said...

Hi Andrejus,
Can I use same code ,if I am loosing current row during activation and passivation

Andrejus Baranovskis said...

This is very good question - I will test it and let you know.


Andrejus Baranovskis said...


You should not loose current row during activation/passivation by design, ADF ensures that current row will be preserved during activation/passivation.