no cache policy header, USE_APPLICATION_VIEW_CACHE not working properly

Problem : 
When I try to open a dialog box from my  page, I get the following error.


Apr 2, 2010 12:24:22 PM oracle.webcache.adf.config.AFCConfigFactory getConfig
INFO: ADF Config did not find the AFC config 
Apr 2, 2010 12:24:22 PM oracle.webcache.adf.config.AFCConfigFactory getConfig
SEVERE: Error in config : Cannot locate config file. Using default values
Apr 2, 2010 12:24:22 PM oracle.webcache.adf.config.AFCConfigFactory getConfig
SEVERE: Error in config. Using default values
Apr 2, 2010 12:24:22 PM oracle.webcache.adf.filter.PageCachingProcessor getResponseFromCache
INFO: page (__ADFv__) cache miss
Apr 2, 2010 12:24:22 PM oracle.webcache.adf.filter.PageCachingProcessor isResponseCacheable
INFO: response not cacheable - no cache policy header
Apr 2, 2010 12:24:22 PM oracle.webcache.adf.filter.PageCachingProcessor getResponseFromCache
INFO: page (PPAPListDialog.jspx) cache miss
Apr 2, 2010 12:24:22 PM aam.tooling.managedbeans.LoggedUserInfo
INFO: In Logged User Info Bean...
Apr 2, 2010 12:24:22 PM oracle.webcache.adf.filter.PageCachingProcessor isResponseCacheable
INFO: response not cacheable - no cache policy header


Due to this error, the following things happen.

• I keep on getting the Row Currency Error on navigating time and again to my dialog pages.
• I have an attachment dialog with command link to save the attachment on user's system. It often refers to the firstly clicked attachment always even when I have clicked on the different link this time.
• It does not update the dialog view properly. Sometimes newly added rows do not get displayed there.

Solution :
After a long study it was clear that it has something to do with the cache. But I just wondered where. Finally it was  USE_APPLICATION_VIEW_CACHE in the web.xml file. I set it to false and all the above mentioned errors went.
    <context-param>
        <param-name>oracle.adf.view.faces.USE_APPLICATION_VIEW_CACHE</param-name>
        <param-value>false</param-value>
    </context-param>

Although more information about USE_APPLICATION_VIEW_CACHE  can be found here but there is no reference that I could make why this be causing problem in my application. But still if you face the same problem (probably when it's a day before the UAT as in my case), you can give a thought to apply this solution.