ADF BC Session Cached LOV – Understanding Expire Time by Andrejus Baranovskis

Posted: October 6, 2015 in JDeveloper & ADF
Tags: , , , , , ,
 

clip_image002ADF BC offers LOV caching feature. There are two caching levels – application and session. With application level enabled, it makes LOV rows available for all users. On contrary for session level LOVs, data is cached for single session only. In this post I will focus on session level LOV’s and I’m going to explain when cached data expires and is re-fetched.
You can configure caching level for LOV’s in Model.jpx file, open AppModules section and select appropriate caching level for AM. I will be using Session level. Key point to understand – session level caching for LOV is nothing to do with Web user session lifetime. Session here is AM session, and cache remains in memory only until AM session remains assigned to the current user session:

LOV with caching feature is defined a bit differently, List Data Source must be selected from shared AM, other steps are the same: Read the complete article here.

WebLogic Partner Community

For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Forum Wiki

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s