What do you think about factoring the multipart handling in a command for backwards compatibility. Also it
would give the users two options - Command or Filter?
I'd say the main argument for using command (and I don't think it's a decisive argument) is that we can bundle support for it in the default chain, while with a filter, we'd have to lead people through one extra configuration step.
At 9:22 PM -0800 2/24/05, Martin Cooper wrote:
> What do you think about factoringthe multipart handling in a command for backwards compatibility. Also it would give the users two options - Command or Filter? As long as both work in the same way, so that when the population mechanism is hit either would work.
How would this work? I can see parsing the input stream in a command, but I don't see how we'd then be able to change Chain's mind about what request object it hands out, so that it would subsequently hand out the wrapped one.
We could add a "setRequest" method to ServletActionContext. It seems risky when important values are stored in the request, in that if someone put a completely different request in, instead of a wrapped one, certain attributes would just disappear. But it might work, if people were clear that you shouldn't do that!
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]
