[
https://issues.apache.org/jira/browse/JS2-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ate Douma reopened JS2-932:
---------------------------
Assignee: Ate Douma (was: Vivek Kumar)
The real cause of this issue, not evicting user content caches upon
authentication, is still not fixed when not creating a new session upon
authentication (although that's the default now).
As I'm deep in the content cache handling already for integrating public render
parameters cache management, I noticed we do have the proper evicting already
coded upon session invalidation within JetspeedServlet.
As the evicting requires 3 different Spring components and several lines of
logic, I'll move the code from JetspeedServlet to a new UserContentCacheManager
with a single evictUserContentCache method.
This method then needs to be invoked from the following situations:
- JetspeedServlet.sessionDestroyed
- LoginRedirectorServlet.doGet (after container authentication)
- PortalFilter and ShibbolethPortalFilter doFilter (after custom authentication)
- and should also be called by any other custom PortalFilter
Configuration of the UserContentCacheManagerImpl will be done in cache.xml
> 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: Ate Douma
> 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]
