The flex cache caches the HTML output of JSPs in the memory (RAM) of your server. We demonstrate different variants of caching. Therefore, we include two JSPs into each other, both showing the current time. Playing with the cache directives set at the JSPs, the time is refreshed differently. Futhermore, we show how navigations should be cached.
Related links
1 The result
Below you find three examples. Each example is a dynamic function, whose provider JSP includes another JSP. Reload this page in the online project and see how time changes (or not). Also note, that the navigation renders differently on different pages. For each page one version is cached.
File: include-example1.jsp
The Date is Tue Nov 05 11:45:45 CET 2024
Cache properties: never
File: include-target1.jsp
The Date is Tue Nov 05 11:45:45 CET 2024
Cache properties: timeout=1
File: include-example2.jsp
The Date is Tue Nov 05 11:45:45 CET 2024
Cache properties: always
File: include-target2.jsp
The Date is Tue Nov 05 11:45:45 CET 2024
Cache properties: never
A sample navigation
Cache properties: uri
Pages on the current navigation level:
2 Example resources and the interesting spots
The interesting parts here are not the JSPs itself, but the properties set there.
If you are offline: Open the workplace's explorer view in the root site and go to the following folder to see the resources used in the examples:
In this folder, you find all the used resources. Right-click on a resource and choose "Properties" in the context menu to view the properties. In the "Individual properties" tab you find the cache settings.
To see that the JSP's output is really cached, go to the workplace's administration view and choose "Cache Administration". In the frame "Browse cache contents", click "Flex Cache". Then you find a listing of all flex-cache entries. Click on "Variations" (upper-right corner of the listing) to see the different variations that are cached.