I think its worth delegating to the service impl. That offers
implementers the most flexibility. we should obviously implement spec
compliant behavior in the default service.
Nice catch,
E
Eric Dalquist wrote:
For this issue is the check something Pluto should be doing itself? My
assumption here would be that if getRemoteUser() returns null the user
is not authenticated. If we need to delegate that check to the portal
via the call to the UserInfoService that works too just wondering if it
is even worth doing the call if there is no remote user.
-Eric
Eric Dalquist (JIRA) wrote:
PortletRequestImpl throws a NullPointerException when getting
USER_INFO for unauthenticated users
-------------------------------------------------------------------------------------------------
Key: PLUTO-477
URL: https://issues.apache.org/jira/browse/PLUTO-477
Project: Pluto
Issue Type: Bug
Components: portlet container
Reporter: Eric Dalquist
Fix For: 1.1.5
PLT.17.2 states:
If the request is done in the context of an un-authenticated user,
calls to the getAttribute method of the request using the USER_INFO
constant must return null.
Currently the PortletRequestImpl.createUserInfoMap() does not handle
the case of UserInfoService.getUserInfo returning null for an
unauthenticated user and will throw a NullPointerException in this case.
