Charles Severance wrote:
That was my first suspicion too - so I added the user-attribute entries - but it still did not work.

Now in the light of day - I realized that the user-attribute entries needed to be in <portlet-app> - not <portlet> :)

So now I have them in the right place and viola - it all works.  Thanks.

I might just comment that PLT.17 is really silly in its wording. It talks of "mapping" - there is no mapping going on in user-attributes - it is just filtering.

Thanks for the clarification. . .I had read through that part of the spec when I first did the impl and the reason I wondered if I was 100% done or not was because I couldn't figure out why all I was doing was filtering :) and no mapping!

Glad to hear it works.

David


There is real mapping in security-role-ref (PLT.20) - but 286 should reword PLT.17 to talk of filtering not mapping.

/Chuck

On Mar 12, 2007, at 8:15 AM, David H. DeWolf wrote:

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




Reply via email to