Jetspeed 2
  1. Jetspeed 2
  2. JS2-1169

The Portlet 2.0 API, PortletResponse#setProperty(String key, String value), doesn't work for cached portlet content.

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: 2.2.0
    • Fix Version/s: 2.2.2
    • Component/s: Aggregation
    • Labels:
      None

      Description

      When a portlet invokes PortletResponse#setProperty(String key, String value) or PortletResponse#addProperty(String key, String value) Portlet 2.0 API methods to set/add a http header, if the portlet content is cached, then the header is not sent to the browser.
      I think the headers should be managed with the portlet content.
      Also, I think the method, PortletResponse#addProperty(Cookie cookie) should be treated in the same way.

        Activity

        Hide
        Woonsan Ko added a comment -

        I had another thought about this.
        This problem seems to be a kind of tricky corner case.
        Anyway, the situation is not ideal, but that's not so bad either because developers can choose workarounds such as having a non-caching header adding portlet whether or not it is visible, whether it is added by a fragment or by header template.
        Therefore, I think it seems good enough to record this case here instead of trying to fix this too ideally.

        Show
        Woonsan Ko added a comment - I had another thought about this. This problem seems to be a kind of tricky corner case. Anyway, the situation is not ideal, but that's not so bad either because developers can choose workarounds such as having a non-caching header adding portlet whether or not it is visible, whether it is added by a fragment or by header template. Therefore, I think it seems good enough to record this case here instead of trying to fix this too ideally.

          People

          • Assignee:
            Woonsan Ko
            Reporter:
            Woonsan Ko
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development