[gatein-issues] [JBoss JIRA] Resolved: (GTNPC-23) If no cache level is set by a portlet for a resource URL, it should default to the parent resource cache level or PAGE if there is none.
Chris Laprun (JIRA)
jira-events at lists.jboss.org
Wed Aug 4 16:19:49 EDT 2010
[ https://jira.jboss.org/browse/GTNPC-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Laprun resolved GTNPC-23.
-------------------------------
Fix Version/s: 2.1.1-GA
Resolution: Rejected
Turns out this was already done, as checked by DowngradeCacheabilityTestCase
> If no cache level is set by a portlet for a resource URL, it should default to the parent resource cache level or PAGE if there is none.
> ----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: GTNPC-23
> URL: https://jira.jboss.org/browse/GTNPC-23
> Project: GateIn Portlet Container
> Issue Type: Bug
> Affects Versions: 2.1.1-GA
> Reporter: Chris Laprun
> Fix For: 2.1.1-GA
>
>
> Per the JSR 286 spec (PLT.13.7):
> If no cachability is set on the resource URL, the cacheability setting of the parent resource is used. If no parent resource is available, PAGE is the default.
> This doesn't seem to be currently the case in the code, where the cacheability setting stays null if setCacheability is not called on ResourceURL.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the gatein-issues
mailing list