clearCache: Entity based View Object and transient View Object Scenario

clearCache: Entity based View Object and transient View Object Scenario

原文： http://blogs.oracle.com/vijaymohan/entry/clearcache_entity_based_view_object_and_transient_view_object_scenario#

Most of us feel that clearCache() on a viewObject is just a low key affair involving the flushing  out of VO rows from the cache but when you actually dig into the intricacies involved then you will find that there are quite a few operations involved under the covers.
here is the account of that -

Entity Object Based View Object Scenario:

For entity object based view object when we do a clearCache() then it force executes the executeQuery() for that VO to refresh the entity and view object cache from database.

There are two properties in your AM involving clearcahe:

1.clearCacheOnRollback - Whenever you do a AM rollback then all the underlying VO cache would be refreshed from DB, irrespective of any newly created rows.

Now, if you want to override this standard framework behavior then -

a). You need to override the following in the AMImpl Class:
     override afterRollback() and beforeRollback() methods and comment out the super() call.
     Write your own logic to do conditional/selective rollback of view objects.

b) The alternative approach of doing this could be -
   b1).As the AMImpl's rollback() internally calls individual  VO's Rollback() , so you can override the afterRollback() and beforeRollback() methods in VOImpl Class. Comment out the super() call and implement you logic to do conditional rollback for that VO.

This way, you can control the clearCache() for the specific VOs whose cache you want to retain even on AM rollback.

2.clearCacheOnCommit() - clearCache() on commit actually refreshes the entity and view object cache from database but at the same time it retains any newly created/ modified rows.

If you want to control the clearCache on Commit() then similarly you can overide the afterCommit() and beforeCommit() methods in resp VOImpl classes.

Transient View Object scenario:

For transient VO also the behavior is same but -

1.If you have set that "no rows has to be fetched" then the framework never force executes the executeQuery() even on clearCache(). This particular scenario I have encountered in the due course of development.

 - So, in this particular scenario when "no rows to be fetched" flag is set and you want to clear your transient VO cache before every progrmmatic population then you need to explictly call the VO.executeQuery(), so that it clears the underlying cache.

2.If the "no. of rows to be fetched" is non-zero then the clearCache() should force execute the VO query and your VO cache should be flushed out.