[ 
https://issues.apache.org/jira/browse/WW-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177950#comment-15177950
 ] 

Filippo Munafò commented on WW-4610:
------------------------------------

It's the same patch I was using locally, it's ok.
I probably also found where the context is updated going through the execute 
phase:

Dispatcher.createContextMap(Map requestMap,
                                    Map parameterMap,
                                    Map sessionMap,
                                    Map applicationMap,
                                    HttpServletRequest request,
                                    HttpServletResponse response,
                                    ServletContext servletContext)

[...]
extraContext.put(StrutsStatics.HTTP_REQUEST, request);
[...]

I do not know if now, with the patch in place, it is right that the update is 
also made there, take a look if you want.

Thanks for the patch,
Filippo

> ServletActionContext.getRequest() doesn't return the MultiPartRequestWrapper 
> (or StrutsRequestWrapper) when using StrutsPrepareFilter
> -------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: WW-4610
>                 URL: https://issues.apache.org/jira/browse/WW-4610
>             Project: Struts 2
>          Issue Type: Bug
>    Affects Versions: 2.3.24, 2.5
>            Reporter: Filippo Munafò
>             Fix For: 2.3.25, 2.5
>
>
> MultiPartRequestWrapper (or StrutsRequestWrapper) is created in 
> Dispatcher.wrapRequest but, there, it's not updated in ServletActionContext. 
> Probably the update is done later because FileUploadInterceptor.intercept has 
> access to the correct object; but using only StrutsPrepareFilter (instead of 
> an execute one) the method ServletActionContext.getRequest() never return the 
> MultiPartRequestWrapper (or StrutsRequestWrapper).



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

Reply via email to