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

Wes Wannemacher updated WW-3363:
--------------------------------

    Component/s: Documentation
        Summary: MultiPartRequest documentation needs updated per 2.1.8 
enhancements  (was: Custom struts.multipart.parser is ignored as of 2.1.8)

Updating issue to reflect necessary documentation updates

> MultiPartRequest documentation needs updated per 2.1.8 enhancements
> -------------------------------------------------------------------
>
>                 Key: WW-3363
>                 URL: https://issues.apache.org/struts/browse/WW-3363
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 2.1.8
>            Reporter: Lauri Lehtinen
>
> This issue appears when I update my struts2 dependency from 2.1.6 to 2.1.8, 
> and disappears when reverting. Here are some facts I've gathered so far:
> In my struts.xml:
> <constant name="struts.multipart.parser" 
> value="com.systemout.pdf.webapp.base.multipart.MonitoredMultiPartRequest" />
> Tomcat startup:
> ...
> 09-12-31 13:36:54 DEBUG org.apache.struts2.config.BeanSelectionProvider - 
> Choosing bean (class 
> com.systemout.pdf.webapp.base.multipart.MonitoredMultiPartRequest) for 
> interface org.apache.struts2.dispatcher.multipart.MultiPartRequest
> ...
> On file upload, debugging in org.apache.struts2.dispatcher.Dispatcher.java, 
> after line 697 has been executed, multiNames contains: [default, jakarta, 
> struts] and multipartHandlerName is set to "jakarta"
> My custom MonitoredMultiPartRequest is never instantiated, instead, 
> JakartaMultiPartRequest is used.

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

Reply via email to