Oracle Portal HTML Templates (Page Skins and Content Layouts) - Cache
By M&S Consulting (Ashok) on May 17th, 2009
Filed Under Technical Tips // Tags: oracle application server, oracle portal
Filed Under Technical Tips // Tags: oracle application server, oracle portal
If you use HTML Templates (Page Skins and/or Content Layouts) on your Oracle Portal implementations, you might notice that they are cached often.
If you want the results/rendering to change more often for these components, you might want to disable the page cache or tweak the webcache settings appropriately.
Related Information:
- Oracle ADF Faces 10g: Submitting a part of the page Did you know ADF Faces allows you to submit only part of a page? This can be useful when you...
- Oracle Portal 10.1.4 or 10.1.4.1 Upgrade to 10.1.4.2 - Features and Bug Fixes You may have applied or are considering applying the Oracle Application Server 10.1.2.3 patch for a variety of reasons. As...
- Oracle IdM - SAML SSO with Google Apps We recently integrated Oracle IdM with the SAML SSO Service from Google Apps. Now customers can continue to authenticate against...
- Oracle VM Templates Firewall Policy Many Oracle VM templates come with a default firewall policy turned on. Â You can disable it by running the...
- Google Apps SSO and SAML M&S has taken our years of Identity Management with products from companies like Oracle to integrate with Google’s popular “Google...
May 19, 2009
that will kill performance!
Instead, look at whether the UI template is the beat place for that dynamic content.
May 19, 2009
Indeed, the implementer should consider performance in all development choices that are made, including that to turn off caching on a page.
Of course, this article assumes you have already made the choice and decision to implement certain functionality inside a page skin or content layout.