Chuck,
this could be the "mapping/filtering" logic that's required by the spec.
are your user attributes registered in the portlet.xml? It was
implemented in phases (and I'm not convinced it's 100% done yet).
David
Charles Severance wrote:
I swear that I had UserInfo working in a pre-release in 1.1.1 and then
it started failing. Here is what happens:
I happily have my UserInfoService Implementation in My
OptionalContainerServices implementation - and my service code gets
called and right before it returns the user info to the container it
happily prints out a nicely populated user info object.
Then back in my portlet - the user info object is null. Here is some
debug print:
sakai.view=snoop.test
Found Current User=csev
(fomr my service)
[EMAIL PROTECTED],
[EMAIL PROTECTED], user.name.given=Charles,
user.name.family=Severance, user.name.nickName=Charles Severance}
(from my Portlet) UserInfo = {}
Map userInfo = (Map)
request.getAttribute(PortletRequest.USER_INFO);
System.out.println("UserInfo = "+userInfo);
I swear this was working with the 1.1.1 trunk and then broke just before
the 1.1.1 release.
I will look into it - just thought this might ring some bells.
/Chuck
