[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-2723) Page fragment caching for plugin render
[ http://jira.jboss.com/jira/browse/JBSEAM-2723?page=all ]
Christian Bauer closed JBSEAM-2723.
-----------------------------------
Fix Version/s: 2.1.0.GA
Resolution: Done
Plugins can now define cache regions in their descriptor:
<cache-regions>
<cache-region name="DirectoryToc">
<invalidation-event name="Node.persisted"/>
<invalidation-event name="Node.removed"/>
<invalidation-event name="Node.updated"/>
</cache-region>
</cache-regions>
And use this (with variations) in their templates:
<s:cache
region="#{currentMacro.getCacheRegion('DirectoryToc')}"
key="#{currentMacro.cacheKey}">
...
Page fragment caching for plugin render
---------------------------------------
Key: JBSEAM-2723
URL: http://jira.jboss.com/jira/browse/JBSEAM-2723
Project: Seam
Issue Type: Task
Components: Wiki
Reporter: Christian Bauer
Assigned To: Christian Bauer
Priority: Blocker
Fix For: 2.1.0.GA
The infrastructure for page fragment caching with EHCache is in place. We need to cache
plugin-rendered HTML fragments with this strategy:
- generate a unique cache key for each plugin, including the document ID and the macro
hashcode (including position and parameters)
- use a separate region for each plugin type, so that we can invalidate the cache for the
whole region ("remove all cached fragments of a certain plugin no matter on what
document it is rendered")
- build cache regions on startup based on plugin metadata
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira