You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Ate Douma (JIRA)" <ji...@apache.org> on 2010/10/16 03:30:34 UTC

[jira] Closed: (PLUTO-598) Retrieving Portlet invoked servlet request attributes should first check PortletRequest attributes before using fallback to the web container

     [ https://issues.apache.org/jira/browse/PLUTO-598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ate Douma closed PLUTO-598.
---------------------------

    Resolution: Fixed

> Retrieving Portlet invoked servlet request attributes should first check PortletRequest attributes before using fallback to the web container 
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: PLUTO-598
>                 URL: https://issues.apache.org/jira/browse/PLUTO-598
>             Project: Pluto
>          Issue Type: Bug
>          Components: portlet container
>    Affects Versions: 2.0.2
>            Reporter: Ate Douma
>            Assignee: Ate Douma
>             Fix For: 2.0.3, 2.1.0
>
>
> 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. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.