[JBoss JIRA] Created: (JBPORTAL-1831) New user properties (locale) set by the user is not immediately used by the portal (improve existing solution)
7:50 a.m.
New user properties (locale) set by the user is not immediately used by the portal
(improve existing solution)
--------------------------------------------------------------------------------------------------------------
Key: JBPORTAL-1831
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1831
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.6.2 Final
Reporter: Thomas Heute
Assigned To: Thomas Heute
Fix For: 2.6.3 Final
Because of some user properties caching, when a user modifies his profile, the new data is
not immediately accessible, only after a re-login
--
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:52 a.m.
New subject: [JBoss JIRA] Updated: (JBPORTAL-1831) New user properties (locale) set by the user is not immediately used by the portal (improve existing solution)
[ http://jira.jboss.com/jira/browse/JBPORTAL-1831?page=all ]
Thomas Heute updated JBPORTAL-1831:
-----------------------------------
Fix Version/s: 2.6.4 Final
(was: 2.6.3 Final)
Affects Version/s: 2.6.3 Final
(was: 2.6.2 Final)
Description:
Because of some user properties caching, when a user modifies his profile, the new data is
not immediately accessible, only after a re-login.
The existing solution isn't great, see: EditProfileAction of core-identity.
1 - the cache flushing shouldn't be done here, it should only mark the profile as
dirty
2 - the JSF update is a workaround for a problem that i could not spot in time for 2.6.3
was:Because of some user properties caching, when a user modifies his profile, the new
data is not immediately accessible, only after a re-login
New user properties (locale) set by the user is not immediately used
by the portal (improve existing solution)
--------------------------------------------------------------------------------------------------------------
Key: JBPORTAL-1831
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1831
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.6.3 Final
Reporter: Thomas Heute
Assigned To: Thomas Heute
Fix For: 2.6.4 Final
Because of some user properties caching, when a user modifies his profile, the new data
is not immediately accessible, only after a re-login.
The existing solution isn't great, see: EditProfileAction of core-identity.
1 - the cache flushing shouldn't be done here, it should only mark the profile as
dirty
2 - the JSF update is a workaround for a problem that i could not spot in time for 2.6.3
--
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:46 a.m.
New subject: [JBoss JIRA] Updated: (JBPORTAL-1831) New user properties (locale) set by the user is not immediately used by the portal (improve existing solution)
[ http://jira.jboss.com/jira/browse/JBPORTAL-1831?page=all ]
Thomas Heute updated JBPORTAL-1831:
-----------------------------------
Fix Version/s: 2.8 Final
(was: 2.6.4 Final)
New user properties (locale) set by the user is not immediately used
by the portal (improve existing solution)
--------------------------------------------------------------------------------------------------------------
Key: JBPORTAL-1831
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1831
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.6.3 Final
Reporter: Thomas Heute
Assigned To: Thomas Heute
Fix For: 2.8 Final
Because of some user properties caching, when a user modifies his profile, the new data
is not immediately accessible, only after a re-login.
The existing solution isn't great, see: EditProfileAction of core-identity.
1 - the cache flushing shouldn't be done here, it should only mark the profile as
dirty
2 - the JSF update is a workaround for a problem that i could not spot in time for 2.6.3
--
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
6107
days inactive
6154
days old
2 comments
1 participants
participants (1)
-
Thomas Heute (JIRA)