This content has been marked as final. Show 2 replies
We are using JDeveloper 188.8.131.52 and JHS 184.108.40.206. The Application modules are derived from JhsApplicationModuleImpl. It looks as though the prepare session does getDBTransaction().setClearCacheOnRollback(false);
We have a taskflow for pop-ups that contains a save and cancel button plus the dynamic region content. The idea is that the save will invoke the return activity that performs a commit. This will also close the popup-window. The cancel button is similar to the save button, but the return activity will end the transaction with a rollback. This seems to notify ALL accessed view objects to issue a rollback. This causes each view object to clear their cache and then re-execute the query.However, when the rollback happens it causes all the active views to be cleared and requeried. This is a performance issue as all the JHS user, module, menu and permission data is requeried.
I have also tried using the taskflow savepoints and the same behaviour is observed.
It seems as though the setClearCacheOnRollback may not be adhered to or the assumption has changed.
I can also look at doing something different, but this seems to be a bit of an issue with the JHS extensions and / or ADF. My something different involves a managed bean that can invoke the actual rollback for the view object in question.