[
https://issues.apache.org/jira/browse/JS2-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Woonsan Ko resolved JS2-1169.
-----------------------------
Resolution: Won't Fix
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.
> 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-unsubscr...@portals.apache.org
For additional commands, e-mail: jetspeed-dev-h...@portals.apache.org
