[JBoss JIRA] Created: (JBPORTAL-1325) ConsumerCacheInterceptor : should not use the cache just after login
3:54 p.m.
ConsumerCacheInterceptor : should not use the cache just after login
--------------------------------------------------------------------
Key: JBPORTAL-1325
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1325
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Portal Core
Environment: jbp 2.4.0
Reporter: Antoine Herzog
Assigned To: Julien Viet
Use case :
- user come to the site.
- Portlet show views for unchecked user. These views are put in the cache.
- user log in, let's say as admin
- the cached views still show the previous things, not taking into account the change of
authorizations
- the user can't see the proper things
usual needs :
- for I18n portals : change of locale when user log in. all the portlets must do the
change, not depending on cache
- for admin or special roles features in the portlet views
- for modes depending on roles (see forum post)
In the default portal, there are no use of cache. so all these use cases are fullfiled.
to reproduce the problem :
- put some cache on the user portlet (great feature for prod), the user portlet window
may not update after logging.
resolution :
in the ConsumerCacheInterceptor
the CacheKey do not take into account the login state.
see : public CacheKey(StateString navigationalState, WindowState windowState, Mode mode)
so store the user name (or "unchecked") in the CacheEntry.
put the parameter "userOfFragment" in the CacheKey.
when retrieving the CacheEntry, compare the currentUser and the userOfFragment, and
don't use the cache if different.
just to see : can we have access to the logued user in this interceptor ? (that, i
don't know)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:02 p.m.
New subject: [JBoss JIRA] Commented: (JBPORTAL-1325) ConsumerCacheInterceptor : should not use the cache just after login
[ http://jira.jboss.com/jira/browse/JBPORTAL-1325?page=comments#action_1235... ]
Antoine Herzog commented on JBPORTAL-1325:
------------------------------------------
precision : default portal : some portlets have some cache, but when it is not critical.
UserPortlet have no cache.
Administration portlet has -1 cache, but you get it always after login.
ConsumerCacheInterceptor : should not use the cache just after login
--------------------------------------------------------------------
Key: JBPORTAL-1325
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1325
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Portal Core
Environment: jbp 2.4.0
Reporter: Antoine Herzog
Assigned To: Julien Viet
Use case :
- user come to the site.
- Portlet show views for unchecked user. These views are put in the cache.
- user log in, let's say as admin
- the cached views still show the previous things, not taking into account the change of
authorizations
- the user can't see the proper things
usual needs :
- for I18n portals : change of locale when user log in. all the portlets must do the
change, not depending on cache
- for admin or special roles features in the portlet views
- for modes depending on roles (see forum post)
In the default portal, there are no use of cache. so all these use cases are fullfiled.
to reproduce the problem :
- put some cache on the user portlet (great feature for prod), the user portlet window
may not update after logging.
resolution :
in the ConsumerCacheInterceptor
the CacheKey do not take into account the login state.
see : public CacheKey(StateString navigationalState, WindowState windowState, Mode mode)
so store the user name (or "unchecked") in the CacheEntry.
put the parameter "userOfFragment" in the CacheKey.
when retrieving the CacheEntry, compare the currentUser and the userOfFragment, and
don't use the cache if different.
just to see : can we have access to the logued user in this interceptor ? (that, i
don't know)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:08 p.m.
New subject: [JBoss JIRA] Commented: (JBPORTAL-1325) ConsumerCacheInterceptor : should not use the cache just after login
[ http://jira.jboss.com/jira/browse/JBPORTAL-1325?page=comments#action_1236... ]
Julien Viet commented on JBPORTAL-1325:
---------------------------------------
does it still happen in 2.6 ?
ConsumerCacheInterceptor : should not use the cache just after login
--------------------------------------------------------------------
Key: JBPORTAL-1325
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1325
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Portal Core
Environment: jbp 2.4.0
Reporter: Antoine Herzog
Assigned To: Julien Viet
Fix For: 2.8 Final, 2.6.1 Final
Use case :
- user come to the site.
- Portlet show views for unchecked user. These views are put in the cache.
- user log in, let's say as admin
- the cached views still show the previous things, not taking into account the change of
authorizations
- the user can't see the proper things
usual needs :
- for I18n portals : change of locale when user log in. all the portlets must do the
change, not depending on cache
- for admin or special roles features in the portlet views
- for modes depending on roles (see forum post)
In the default portal, there are no use of cache. so all these use cases are fullfiled.
to reproduce the problem :
- put some cache on the user portlet (great feature for prod), the user portlet window
may not update after logging.
resolution :
in the ConsumerCacheInterceptor
the CacheKey do not take into account the login state.
see : public CacheKey(StateString navigationalState, WindowState windowState, Mode mode)
so store the user name (or "unchecked") in the CacheEntry.
put the parameter "userOfFragment" in the CacheKey.
when retrieving the CacheEntry, compare the currentUser and the userOfFragment, and
don't use the cache if different.
just to see : can we have access to the logued user in this interceptor ? (that, i
don't know)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:08 p.m.
New subject: [JBoss JIRA] Updated: (JBPORTAL-1325) ConsumerCacheInterceptor : should not use the cache just after login
[ http://jira.jboss.com/jira/browse/JBPORTAL-1325?page=all ]
Julien Viet updated JBPORTAL-1325:
----------------------------------
Fix Version/s: 2.6.1 Final
2.8 Final
please set fix version
ConsumerCacheInterceptor : should not use the cache just after login
--------------------------------------------------------------------
Key: JBPORTAL-1325
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1325
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Portal Core
Environment: jbp 2.4.0
Reporter: Antoine Herzog
Assigned To: Julien Viet
Fix For: 2.8 Final, 2.6.1 Final
Use case :
- user come to the site.
- Portlet show views for unchecked user. These views are put in the cache.
- user log in, let's say as admin
- the cached views still show the previous things, not taking into account the change of
authorizations
- the user can't see the proper things
usual needs :
- for I18n portals : change of locale when user log in. all the portlets must do the
change, not depending on cache
- for admin or special roles features in the portlet views
- for modes depending on roles (see forum post)
In the default portal, there are no use of cache. so all these use cases are fullfiled.
to reproduce the problem :
- put some cache on the user portlet (great feature for prod), the user portlet window
may not update after logging.
resolution :
in the ConsumerCacheInterceptor
the CacheKey do not take into account the login state.
see : public CacheKey(StateString navigationalState, WindowState windowState, Mode mode)
so store the user name (or "unchecked") in the CacheEntry.
put the parameter "userOfFragment" in the CacheKey.
when retrieving the CacheEntry, compare the currentUser and the userOfFragment, and
don't use the cache if different.
just to see : can we have access to the logued user in this interceptor ? (that, i
don't know)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:17 a.m.
New subject: [JBoss JIRA] Commented: (JBPORTAL-1325) ConsumerCacheInterceptor : should not use the cache just after login
[ http://jira.jboss.com/jira/browse/JBPORTAL-1325?page=comments#action_1236... ]
Antoine Herzog commented on JBPORTAL-1325:
------------------------------------------
For what I remember, you explained somewhere (forum ?) that the cache was stored in the
session, so login change are taken into account implicitly (cache follow the session
lifecycle).
So this is not an issue. (I did this jira in march when exploring things about cache).
Should be closed.
just in case, I don't know about 2.6 (not upgraded yet my cache features for nav menu
etc...)
but if the cache is still in session (still no change, no use of JBoss Cache ?), it should
be still ok.
ConsumerCacheInterceptor : should not use the cache just after login
--------------------------------------------------------------------
Key: JBPORTAL-1325
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1325
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Portal Core
Environment: jbp 2.4.0
Reporter: Antoine Herzog
Assigned To: Julien Viet
Fix For: 2.8 Final, 2.6.1 Final
Use case :
- user come to the site.
- Portlet show views for unchecked user. These views are put in the cache.
- user log in, let's say as admin
- the cached views still show the previous things, not taking into account the change of
authorizations
- the user can't see the proper things
usual needs :
- for I18n portals : change of locale when user log in. all the portlets must do the
change, not depending on cache
- for admin or special roles features in the portlet views
- for modes depending on roles (see forum post)
In the default portal, there are no use of cache. so all these use cases are fullfiled.
to reproduce the problem :
- put some cache on the user portlet (great feature for prod), the user portlet window
may not update after logging.
resolution :
in the ConsumerCacheInterceptor
the CacheKey do not take into account the login state.
see : public CacheKey(StateString navigationalState, WindowState windowState, Mode mode)
so store the user name (or "unchecked") in the CacheEntry.
put the parameter "userOfFragment" in the CacheKey.
when retrieving the CacheEntry, compare the currentUser and the userOfFragment, and
don't use the cache if different.
just to see : can we have access to the logued user in this interceptor ? (that, i
don't know)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:24 a.m.
New subject: [JBoss JIRA] Commented: (JBPORTAL-1325) ConsumerCacheInterceptor : should not use the cache just after login
[ http://jira.jboss.com/jira/browse/JBPORTAL-1325?page=comments#action_1236... ]
Julien Viet commented on JBPORTAL-1325:
---------------------------------------
Actually cached markup is stored in session but it is keyed by the user principal name
which avoid such issues, that's why I am asking you to check.
ConsumerCacheInterceptor : should not use the cache just after login
--------------------------------------------------------------------
Key: JBPORTAL-1325
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1325
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Portal Core
Environment: jbp 2.4.0
Reporter: Antoine Herzog
Assigned To: Julien Viet
Fix For: 2.8 Final, 2.6.1 Final
Use case :
- user come to the site.
- Portlet show views for unchecked user. These views are put in the cache.
- user log in, let's say as admin
- the cached views still show the previous things, not taking into account the change of
authorizations
- the user can't see the proper things
usual needs :
- for I18n portals : change of locale when user log in. all the portlets must do the
change, not depending on cache
- for admin or special roles features in the portlet views
- for modes depending on roles (see forum post)
In the default portal, there are no use of cache. so all these use cases are fullfiled.
to reproduce the problem :
- put some cache on the user portlet (great feature for prod), the user portlet window
may not update after logging.
resolution :
in the ConsumerCacheInterceptor
the CacheKey do not take into account the login state.
see : public CacheKey(StateString navigationalState, WindowState windowState, Mode mode)
so store the user name (or "unchecked") in the CacheEntry.
put the parameter "userOfFragment" in the CacheKey.
when retrieving the CacheEntry, compare the currentUser and the userOfFragment, and
don't use the cache if different.
just to see : can we have access to the logued user in this interceptor ? (that, i
don't know)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:18 a.m.
New subject: [JBoss JIRA] Commented: (JBPORTAL-1325) ConsumerCacheInterceptor : should not use the cache just after login
[ http://jira.jboss.com/jira/browse/JBPORTAL-1325?page=comments#action_1236... ]
Antoine Herzog commented on JBPORTAL-1325:
------------------------------------------
ok
I'll try and comment here.
but at the end of upgrade to 2.6 and my new portal feature (priority).
I don't want caching to add problems before to be sure all is working.
ConsumerCacheInterceptor : should not use the cache just after login
--------------------------------------------------------------------
Key: JBPORTAL-1325
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1325
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Portal Core
Environment: jbp 2.4.0
Reporter: Antoine Herzog
Assigned To: Julien Viet
Fix For: 2.8 Final, 2.6.1 Final
Use case :
- user come to the site.
- Portlet show views for unchecked user. These views are put in the cache.
- user log in, let's say as admin
- the cached views still show the previous things, not taking into account the change of
authorizations
- the user can't see the proper things
usual needs :
- for I18n portals : change of locale when user log in. all the portlets must do the
change, not depending on cache
- for admin or special roles features in the portlet views
- for modes depending on roles (see forum post)
In the default portal, there are no use of cache. so all these use cases are fullfiled.
to reproduce the problem :
- put some cache on the user portlet (great feature for prod), the user portlet window
may not update after logging.
resolution :
in the ConsumerCacheInterceptor
the CacheKey do not take into account the login state.
see : public CacheKey(StateString navigationalState, WindowState windowState, Mode mode)
so store the user name (or "unchecked") in the CacheEntry.
put the parameter "userOfFragment" in the CacheKey.
when retrieving the CacheEntry, compare the currentUser and the userOfFragment, and
don't use the cache if different.
just to see : can we have access to the logued user in this interceptor ? (that, i
don't know)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:18 a.m.
New subject: [JBoss JIRA] Updated: (JBPORTAL-1325) ConsumerCacheInterceptor : should not use the cache just after login
[ http://jira.jboss.com/jira/browse/JBPORTAL-1325?page=all ]
Thomas Heute updated JBPORTAL-1325:
-----------------------------------
Fix Version/s: 2.6.2 Final
(was: 2.6.1 Final)
ConsumerCacheInterceptor : should not use the cache just after login
--------------------------------------------------------------------
Key: JBPORTAL-1325
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1325
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Portal Core
Environment: jbp 2.4.0
Reporter: Antoine Herzog
Assigned To: Julien Viet
Fix For: 2.8 Final, 2.6.2 Final
Use case :
- user come to the site.
- Portlet show views for unchecked user. These views are put in the cache.
- user log in, let's say as admin
- the cached views still show the previous things, not taking into account the change of
authorizations
- the user can't see the proper things
usual needs :
- for I18n portals : change of locale when user log in. all the portlets must do the
change, not depending on cache
- for admin or special roles features in the portlet views
- for modes depending on roles (see forum post)
In the default portal, there are no use of cache. so all these use cases are fullfiled.
to reproduce the problem :
- put some cache on the user portlet (great feature for prod), the user portlet window
may not update after logging.
resolution :
in the ConsumerCacheInterceptor
the CacheKey do not take into account the login state.
see : public CacheKey(StateString navigationalState, WindowState windowState, Mode mode)
so store the user name (or "unchecked") in the CacheEntry.
put the parameter "userOfFragment" in the CacheKey.
when retrieving the CacheEntry, compare the currentUser and the userOfFragment, and
don't use the cache if different.
just to see : can we have access to the logued user in this interceptor ? (that, i
don't know)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:55 a.m.
New subject: [JBoss JIRA] Commented: (JBPORTAL-1325) ConsumerCacheInterceptor : should not use the cache just after login
[ http://jira.jboss.com/jira/browse/JBPORTAL-1325?page=comments#action_1237... ]
Thomas Heute commented on JBPORTAL-1325:
----------------------------------------
Antoine, did you check on 2.6 ?
I'm not sure i understood your issue, so i cannot try it myself.
ConsumerCacheInterceptor : should not use the cache just after login
--------------------------------------------------------------------
Key: JBPORTAL-1325
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1325
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Portal Core
Environment: jbp 2.4.0
Reporter: Antoine Herzog
Assigned To: Julien Viet
Fix For: 2.8 Final, 2.6.2 Final
Use case :
- user come to the site.
- Portlet show views for unchecked user. These views are put in the cache.
- user log in, let's say as admin
- the cached views still show the previous things, not taking into account the change of
authorizations
- the user can't see the proper things
usual needs :
- for I18n portals : change of locale when user log in. all the portlets must do the
change, not depending on cache
- for admin or special roles features in the portlet views
- for modes depending on roles (see forum post)
In the default portal, there are no use of cache. so all these use cases are fullfiled.
to reproduce the problem :
- put some cache on the user portlet (great feature for prod), the user portlet window
may not update after logging.
resolution :
in the ConsumerCacheInterceptor
the CacheKey do not take into account the login state.
see : public CacheKey(StateString navigationalState, WindowState windowState, Mode mode)
so store the user name (or "unchecked") in the CacheEntry.
put the parameter "userOfFragment" in the CacheKey.
when retrieving the CacheEntry, compare the currentUser and the userOfFragment, and
don't use the cache if different.
just to see : can we have access to the logued user in this interceptor ? (that, i
don't know)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:43 p.m.
New subject: [JBoss JIRA] Commented: (JBPORTAL-1325) ConsumerCacheInterceptor : should not use the cache just after login
[ http://jira.jboss.com/jira/browse/JBPORTAL-1325?page=comments#action_1237... ]
Antoine Herzog commented on JBPORTAL-1325:
------------------------------------------
This is not an issue..... (I did this jira in march when exploring things about cache...
did not see the thing explained since by Julien).
Should be closed.
(see comments yet above).
about checking : this was asked by Julien, but I think it was "just in case..."
I don't think it is usefull.
not yet using the cache with 2.6 (don't want to add this while starting some ajax
stuff)....
if I see something, I'll reopen this... but sure it won't be necessary.
ConsumerCacheInterceptor : should not use the cache just after login
--------------------------------------------------------------------
Key: JBPORTAL-1325
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1325
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Portal Core
Environment: jbp 2.4.0
Reporter: Antoine Herzog
Assigned To: Julien Viet
Fix For: 2.8 Final, 2.6.2 Final
Use case :
- user come to the site.
- Portlet show views for unchecked user. These views are put in the cache.
- user log in, let's say as admin
- the cached views still show the previous things, not taking into account the change of
authorizations
- the user can't see the proper things
usual needs :
- for I18n portals : change of locale when user log in. all the portlets must do the
change, not depending on cache
- for admin or special roles features in the portlet views
- for modes depending on roles (see forum post)
In the default portal, there are no use of cache. so all these use cases are fullfiled.
to reproduce the problem :
- put some cache on the user portlet (great feature for prod), the user portlet window
may not update after logging.
resolution :
in the ConsumerCacheInterceptor
the CacheKey do not take into account the login state.
see : public CacheKey(StateString navigationalState, WindowState windowState, Mode mode)
so store the user name (or "unchecked") in the CacheEntry.
put the parameter "userOfFragment" in the CacheKey.
when retrieving the CacheEntry, compare the currentUser and the userOfFragment, and
don't use the cache if different.
just to see : can we have access to the logued user in this interceptor ? (that, i
don't know)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:22 p.m.
New subject: [JBoss JIRA] Resolved: (JBPORTAL-1325) ConsumerCacheInterceptor : should not use the cache just after login
[ http://jira.jboss.com/jira/browse/JBPORTAL-1325?page=all ]
Thomas Heute resolved JBPORTAL-1325.
------------------------------------
Resolution: Won't Fix
Assignee: Thomas Heute (was: Julien Viet)
I mark it resolved as "won't fix" then, thanks.
ConsumerCacheInterceptor : should not use the cache just after login
--------------------------------------------------------------------
Key: JBPORTAL-1325
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1325
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Portal Core
Environment: jbp 2.4.0
Reporter: Antoine Herzog
Assigned To: Thomas Heute
Fix For: 2.6.2 Final, 2.8 Final
Use case :
- user come to the site.
- Portlet show views for unchecked user. These views are put in the cache.
- user log in, let's say as admin
- the cached views still show the previous things, not taking into account the change of
authorizations
- the user can't see the proper things
usual needs :
- for I18n portals : change of locale when user log in. all the portlets must do the
change, not depending on cache
- for admin or special roles features in the portlet views
- for modes depending on roles (see forum post)
In the default portal, there are no use of cache. so all these use cases are fullfiled.
to reproduce the problem :
- put some cache on the user portlet (great feature for prod), the user portlet window
may not update after logging.
resolution :
in the ConsumerCacheInterceptor
the CacheKey do not take into account the login state.
see : public CacheKey(StateString navigationalState, WindowState windowState, Mode mode)
so store the user name (or "unchecked") in the CacheEntry.
put the parameter "userOfFragment" in the CacheKey.
when retrieving the CacheEntry, compare the currentUser and the userOfFragment, and
don't use the cache if different.
just to see : can we have access to the logued user in this interceptor ? (that, i
don't know)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6923
days inactive
7068
days old
10 comments
3 participants
participants (3)
-
Antoine Herzog (JIRA) -
Julien Viet (JIRA)
-
Thomas Heute (JIRA)