(Pasted from an earlier answer)
Hello
I noticed the same problem when moving to 1.0. It seems that
the requesthandler notices that the request is a multi-part and
tries to find the multi-part data, even when the request are
already handled and you are only forwarding to the next
action. (I only got the problem when going to another action.)
The way I handled it was to set redirect="true" in struts-config.xml
for the action that I forwarded to, this made the multi-part info
go away from the request (and all other parameters too of course,
so if you are expecting request parameters in the next action this
will not work.)
I guess this could be fixed in the code too, maybe by having the request
reader setting a request attribute so that it knows the next time
that it already has gotten the data. But I did not go deep enough
into the code to know if that is feasible or not.
Regards
Mikael
"MacKellar, Kimberly" wrote:
> I have a form that submits a file to an action (UploadImageAction). After
> the action has finished processing the file it forwards to another Action
> that retrieves data to display a page. When the forward is invoked in
> UploadImageAction I get the following error
> javax.servlet.ServletException: MultipartIterator: no multipart request data
> sent at
> org.apache.struts.upload.MultipartIterator.parseRequest(MultipartIterator.ja
> va:341) at
> org.apache.struts.upload.MultipartIterator.(MultipartIterator.java:152)
>
> Is there a way to reset something in the request to prevent this from
> happening?
>
> Kimberly MacKellar
> Thomson Financial Publishing
> [EMAIL PROTECTED]
> (847) 933-8005
