Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.0.2
-
None
Description
In o.a.pluto.container.impl.HttpServletPortletRequestWrapper.getAttribute(String) a (non path related) attribute currently first is looked up from getRequest().getAttribute(String) with a fallback to the PortletRequest.getAttribute(String).
However, this is the wrong order: first the PortletRequest.getAttribute(String) should be checked to ensure a possibly earlier set attribute which is only set with PortletRequest.setAttribute(String,Object) (and possibly cached there) is returned.