No way to know if expiration cache value was set via PortletDD
--------------------------------------------------------------
Key: PLUTO-448
URL: https://issues.apache.org/jira/browse/PLUTO-448
Project: Pluto
Issue Type: Bug
Components: descriptor
Affects Versions: 1.1.4
Reporter: Eric Dalquist
The PortletDD object defaults the expirationCache property to 0. With this
value there is no way to know if the expiration-cache element was specified in
the portlet descriptor which is needed when implementing support for the
expiration cache request property.
Creating a EXPIRATION_CACHE_UNSET constant set to Integer.MIN_VALUE and
initializing the expirationCache property in the PortletDD object with the
constant provides a means for implementors to determine if the expiration-cache
element was specified.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.