ADF table with non-cached iterator not refreshed; bug or feature?
Situation:
- entity and view object based on hr.employees
- table on a page bound to EmployeesView
- iterator's cacheResults set to false
- a partial submit button on the page, set as table's partial trigger
Scenario:
- user first loads the page
- underlying data in the database is changed
- when the button is pressed, the new data is fetched from the database, but the old data is show on the page after response is completed
Why:
- because EditableValueRenderer.getConvertedString checks if there is submitted value for that field. Even though the user did not change any data, all the values are submitted during partial submit.
Question:
- is this a bug or does it serve a purpose?