Oracle Portal HTML Templates (Page Skins and Content Layouts) – Cache
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 Portal HTML Templates – Page Skins, Content Layouts and More
I have seen a large...
- Oracle Portal Broken with iPhone
SSL with Oracle Application Server...
- Oracle ADF Faces 10g: Submitting a part of the page
Did you know ADF Faces...
- 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...
- Oracle Application Server Version – Verify 10g Upgrade to OracleAS 10.2.3 for Portal 10.1.4.2
There are a couple of...
- Underpowering Oracle Portal 10.1.4 on purpose….and winning.
Our friends at Oracle give...
- Oracle Portal
Following are a few of...
- asp:ControlParameter vs. asp:FormParameter in Master Page
I hit what I considered...
that will kill performance!
Instead, look at whether the UI template is the beat place for that dynamic content.
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.