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

Scott Nicklous resolved PLUTO-630.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 3.0.0

fixed in Pluto implementation

> TCK: HttpServletRequest#getAttributeNames returns incorrect values
> ------------------------------------------------------------------
>
>                 Key: PLUTO-630
>                 URL: https://issues.apache.org/jira/browse/PLUTO-630
>             Project: Pluto
>          Issue Type: Bug
>          Components: portlet container
>            Reporter: Scott Nicklous
>            Priority: Minor
>             Fix For: 3.0.0
>
>
> The JSR 286 spec states that the HttpServletRequest.getAttributeNames must 
> provide the same functionality as the corresponding portlet request function. 
> This fails for all portlet requests, both when a servlet is included and when 
> it is the target of a forward. Failing test cases:
> V2DispatcherReqRespTests2_SPEC2_19_ForwardServletRenderRequest_getAttributeNames
> V2DispatcherReqRespTests2_SPEC2_19_ForwardServletEventRequest_getAttributeNames
> V2DispatcherReqRespTests2_SPEC2_19_ForwardServletActionRequest_getAttributeNames
> V2DispatcherReqRespTests2_SPEC2_19_ForwardServletResourceRequest_getAttributeNames
> V2DispatcherReqRespTests4_SPEC2_19_IncludeServletActionRequest_getAttributeNames
>  
> ... etc. (all "getAttributeNames" tests fail)
> Example failure text:
> V2DispatcherReqRespTests2_SPEC2_19_ForwardServletRenderRequest_getAttributeNames
>  results:
> Test Failed
> Details: In a target servlet of a forward in the Render phase, the method 
> HttpServletRequest.getAttributeNames must provide the same functionality as 
> RenderRequest.getAttributeNames.
> In HttpServletRequest attribute names but not in RenderRequest attribute 
> names:
> javax.servlet.forward.query_string
> Pluto_tck-V2DispatcherReqRespTests2-3.0-SNAPSHOT.DispatcherReqRespTests2_SPEC2_19_ForwardServletRenderRequest!-1450703940|6_javax.portlet.config
> Pluto_tck-V2DispatcherReqRespTests2-3.0-SNAPSHOT.DispatcherReqRespTests2_SPEC2_19_ForwardServletRenderRequest!-1450703940|6_req.attr.test.V2DispatcherReqRespTests2_SPEC2_19_ForwardServletRenderRequest_getAttribute
> Pluto_tck-V2DispatcherReqRespTests2-3.0-SNAPSHOT.DispatcherReqRespTests2_SPEC2_19_ForwardServletRenderRequest!-1450703940|6_req.attr.tid
> Pluto_tck-V2DispatcherReqRespTests2-3.0-SNAPSHOT.DispatcherReqRespTests2_SPEC2_19_ForwardServletRenderRequest!-1450703940|6_javax.portlet.response
> Pluto_tck-V2DispatcherReqRespTests2-3.0-SNAPSHOT.DispatcherReqRespTests2_SPEC2_19_ForwardServletRenderRequest!-1450703940|6_req.attr.test.V2DispatcherReqRespTests2_SPEC2_19_ForwardServletRenderRequest_getAttributeNames
> Pluto_tck-V2DispatcherReqRespTests2-3.0-SNAPSHOT.DispatcherReqRespTests2_SPEC2_19_ForwardServletRenderRequest!-1450703940|6_javax.portlet.request
> In RenderRequest attribute names but not in HttpServletRequest attribute 
> names:
> javax.servlet.include.servlet_path
> javax.servlet.forward.path_info
> javax.servlet.include.context_path
> javax.servlet.include.request_uri



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to