Mailing-List: contact pluto-dev-help@portals.apache.org; run by ezmlm
Precedence: bulk
Reply-To: pluto-dev@portals.apache.org
Reply-To: pluto-dev@portals.apache.org
Message-ID: <1510686123.1109977246662.JavaMail.jira@ajax.apache.org>
Date: Sat, 5 Mar 2005 00:00:46 +0100 (CET)
From: "nik gonzalez (JIRA)" <pluto-dev@jakarta.apache.org>
To: pluto-dev@jakarta.apache.org
Subject: [jira] Created: (PLUTO-113) HttpServletRequest.getAttribute returns
 namespaced attribute names
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

HttpServletRequest.getAttribute returns namespaced attribute names
------------------------------------------------------------------

         Key: PLUTO-113
         URL: http://issues.apache.org/jira/browse/PLUTO-113
     Project: Pluto
        Type: Bug
  Components: portlet container  
    Versions: 1.0.1-rc3    
    Reporter: nik gonzalez


If I set an attribute in the RenderRequest like so: 
request.setAttribute("bob", entity); 

I can (with one exception noted below) read it from the HttpServletRequest in an included JSP/jspTag, thusly: 
Object test3 = pageContext.getRequest().getAttribute("bob"); 

However if I obtain an enumeration of the attribute names: 
Enumeration attrNames = pageContext.getRequest().getAttributeNames(); 

I will see the attribute in a namespaced form. Ie: 
"Pluto_1574_bob" 

When obtaining the enumeration from the RenderRequest the names do not include this namespacing. 

Note the Portlet spec, PLT.16.3.3 "Request and Response objects for Included Servlets/JSPs", on page 67 line 16, wherein it is proclaimed that the method getAttributeNames must be like unto its PortletRequest equivalant. 

Additionally, use of the name "entity" for request attributes doesnt work. It appears the container is using it to remember part of the portlets namespace, and this will silently override any attempt to set a request attribute named "entity".

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira