[jira] Issue Comment Edited: (PLUTO-448) No way to know if expiration cache value was set via PortletDD

["Craig Doremus (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/PLUTO-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552207 ] 

cdoremus edited comment on PLUTO-448 at 12/16/07 6:54 AM:
---------------------------------------------------------------

Added EXPIRATION_CACHE_UNSET expiration cache default in PortletDD to 1.1-286-trunk-merge branch  in SVN rev 604630. Unit test was not added as it compiled with errors due to changes to that class in creating JSR-286 version of it..

      was (Author: cdoremus):
    Added EXPIRATION_CACHE_UNSET expireation cache default in PortletDD  in SVN rev 604630. Unit test was not added as it compiled with errors due to changes to that class in creating JSR-286 version of it..
  
> 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
>            Assignee: Elliot Metsger
>             Fix For: 1.2.0, 1.1.5
>
>         Attachments: pluto_cache.patch
>
>
> 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.