Uploaded image for project: 'Pluto'
  1. Pluto
  2. PLUTO-448

No way to know if expiration cache value was set via PortletDD

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.1.4
    • Fix Version/s: 1.1.5, 2.0.0
    • Component/s: descriptor
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              emetsger Elliot Metsger
              Reporter:
              edalquist Eric Dalquist
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: