I know the population process is currently in RequestUtils - I was proposing moving the multipart processing thats in the RequestUtils's populate() method out of there and into a Command. Although the "wrapped" request isn't currently used in the population mechanism theres no reason why, once the "text" parameters are put into the wrapped request, they couldn't then be accessed like any normal parameter in the population process - that would then just leaves the FormFile items to be handled..
I was thinking that we could have a Multipart Command which does the following... * Wraps the Request * Store the "text" parameters in the "wrapped" request (as RequestUtils's populate() method currently does) * Store the FormFile elements somewhere - either a) add them as a property to the wrapped request or b) just have the Mulitpart handler put into the request. Then the Populate Command would need to do the following... * Call BeanUtils's populate method with a Map of the parameters retrieved from the request. * Retrieve a Map of the FormFile elements from wherever they're stored (either then wrapped request or the multipart handler) and call the BeanUtils's populate method with that Map All you would have to do is have a Chain configured with your own implementation rather than the Multipart Command supplied. Niall ----- Original Message ----- From: "Dakota Jack" <[EMAIL PROTECTED]> Sent: Friday, February 25, 2005 5:43 AM > <SNIP> > On Fri, 25 Feb 2005 02:16:14 -0000, Niall Pemberton > <[EMAIL PROTECTED]> wrote: > > Actually I just realized, if the Multipart stuff was all done in its own > > Command, the point in the process it gets executed can be adjusted just by > > the position in the Chain config - as long as its before the populate > > Command. So that shouldn't be an issue, and theres no real reason for having > > the request wrapped until the multipart processing starts. > > > > Niall > </SNIP> > > The wrapping of the request is not used at all in the population of > the ActionForm and the actual population does not occur in > RequestProcessor but in RequestUtils, as you know. > > Perhaps you mean to speak of the handler and not the wrapper? > > Jack --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
