Joe,
I have rethought recent discussions on multipart requests and have a different proposal. What I would suggest would be to take the whole multipart business out of the framework altogether and to treat it as I think it should be treated, as just another Action.
There is nothing about a multipart request that indicates that it should be take care of in any special manner
That's not entirely true, in that one must be sure to wrap a multipart request in *something* which can deal with the special cases of that encoding type before any attempts are made to read the request input stream.
I cannot think of one reason why the default solution has to be hardwired into the framework. Maybe Martin has some reason that I don't know about.
If nothing else, for compatibility. There are lots of Struts applications built around things being as they are; we can't just rip it out without those applications breaking, and we are committed to maintaining backwards compatibility or making clear, deliberate deprecations with adequate time to adjust.
Forgive me if I don't have it at hand from some previous message; where is Struts preventing you from changing to use some other file upload strategy if you want to? Say you wanted to use Jason Hunter's Multipart Filter... you could install that in your webapp and extend the RequestProcessor to make processMultipart(...) a no-op. Then in your action you cast the request to his MultipartRequestWrapper and use its methods to deal with the file. If there's something I'm missing because I've never actually tried to do this, please speak up -- if we've biffed an extension point, I'd like to know.
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
