[
https://issues.apache.org/jira/browse/JS2-932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696952#action_12696952
]
Ate Douma commented on JS2-932:
-------------------------------
While I expect this change to fix it for now, it might not be enough afterall
with regards to other (new) requirements which we'll have to deal with too.
For instance, the portlet 2.0 spec added shared content caching options
(optional) as well as ETag based content caching, see: JS2-952
Full support of those features is only scheduled for the next 2.2.1 release
however.
Additionally, if a new session is not created upon authentication (maybe when
implementing something like a shopping-card solution) this would still remain
an issue too.
> Portlet cache doesn't get refresh after login
> ---------------------------------------------
>
> Key: JS2-932
> URL: https://issues.apache.org/jira/browse/JS2-932
> Project: Jetspeed 2
> Issue Type: Bug
> Affects Versions: 2.1, 2.1.2, 2.1.3, 2.2.0
> Environment: Tomcat,mysql
> Reporter: Vivek Kumar
> Assignee: Vivek Kumar
> Fix For: 2.2.0
>
>
> Portlet cache doesn't get refresh after login. Portlet keep on showing old
> content until we perform some
> action on portlet.
--
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: [email protected]
For additional commands, e-mail: [email protected]
