VO LOV (and af:selectOneChoice) refresh. Can it be automatic?

Question

Hi!
I'm using the build: JDEVADF_11.1.2.2.0_GENERIC_120418.2212.6183.1
I defined an attribute in a ViewObject to use a LOV.
When the page which uses the such attribute is loaded the current database records/information are loaded with no problem.
But if there is some change in the data from where the LOV comes, it does not reflect in the items available (neither if the underlying record was deleted/inserted/updated). No matter what I do: reload the page, navigate to other and come back and so forth, the only way to refresh the combo box is starting a new session.
Looking at the pagedef I could not find the iterator used to build the list of items in the combo box, but while debugging the page I could find a iterator (in fact a JUIteratorBinding) that had the name of the underlying view (from where the items to populate the combo box come) and an additional "List_XX" in the end of the name where XX is a number that varies with no apparent logic sometimes is 2, sometimes is 13, sometimes is 87 and so forth. So I guessed ADF generates it automatically.
I wrote a small function linked to a button and called from there the iterator refresh method.
Once this was done the refresh is processed and everything looks fine for all operations in the underlying data (insert/update/delete).
While I found a partial solution, it looks too much complicated.
What I mean is: Do we need to have all this amount of work to get a simple combo box refreshed?
Is there any approach that is simpler?
I can't believe that a framework like ADF don't have an easier way to solve this use case, but I read the documentation and searched a lot this forum and found no solution, although many posts helped me in building this "solution" (did I miss something?).

Answer 1

Duplicate af:selectOneChoice refresh problem