You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "David Sean Taylor (JIRA)" <je...@portals.apache.org> on 2010/04/02 01:18:27 UTC
[jira] Updated: (JS2-1169) The Portlet 2.0 API,
PortletResponse#setProperty(String key, String value), doesn't work for
cached portlet content.
[ https://issues.apache.org/jira/browse/JS2-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Sean Taylor updated JS2-1169:
-----------------------------------
Fix Version/s: 2.2.2
> 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
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org