portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Woonsan Ko (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] [Assigned] (JS2-1169) The Portlet 2.0 API, PortletResponse#setProperty(String key, String value), doesn't work for cached portlet content.
Date Wed, 14 Sep 2011 18:54:08 GMT

     [ https://issues.apache.org/jira/browse/JS2-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Woonsan Ko reassigned JS2-1169:
-------------------------------

    Assignee: Woonsan Ko

> The Portlet 2.0 API, PortletResponse#setProperty(String key, String value), doesn't work
for cached portlet content.
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: JS2-1169
>                 URL: https://issues.apache.org/jira/browse/JS2-1169
>             Project: Jetspeed 2
>          Issue Type: Bug
>          Components: Aggregation
>    Affects Versions: 2.2.0
>            Reporter: Woonsan Ko
>            Assignee: Woonsan Ko
>             Fix For: 2.2.2
>
>
> 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.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Mime
View raw message