portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ate Douma (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Commented: (JS2-1088) UserInfoManager implementation needs inprovements in resolving mapped user attributes and its cache handling
Date Tue, 02 Mar 2010 21:39:27 GMT

    [ https://issues.apache.org/jira/browse/JS2-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840335#action_12840335
] 

Ate Douma commented on JS2-1088:
--------------------------------

I've implemented cache invalidation handling now too through a RegistryEventListener implemented
by the UserInfoManager itself which will clear cached user attribute map definition on portlet
application change or removal.

For the back port to Jetspeed 2.1.4, almost all 2.2.1 code could be reused (without generics)
except that 2.1.4 still is based off Java Preferences back end storage.
To reproduce logic similar to what is used for 2.2.1, which provides direct access to a logged
on user infoMap through its UserPrincipal, for 2.1.4 I've implemented a similar session backed
user InfoMap based on one-time loading of the User preferences.

> UserInfoManager implementation needs inprovements in resolving mapped user attributes
and its cache handling
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: JS2-1088
>                 URL: https://issues.apache.org/jira/browse/JS2-1088
>             Project: Jetspeed 2
>          Issue Type: Improvement
>          Components: Container
>    Affects Versions: 2.1.3, 2.2.0
>            Reporter: Ate Douma
>            Assignee: Ate Douma
>            Priority: Minor
>             Fix For: 2.1.4, 2.2.1
>
>
> The UserInfoManager currently doesn't properly maintain a cache of mapped (linked) attributes
for a portlet application as there are some bugs in the code.
> Furthermore, I discovered the UserInfoManager didn't work when logging was set to DEBUG
(it throws a NPE then).

-- 
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: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Mime
View raw message