The ActionMapping will be "frozen" and trying to set the input will throw an exception. You could get round this by overriding the processMapping() method and returning a "clone" of the ActionMapping.
Niall ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <dev@struts.apache.org> Sent: Wednesday, February 02, 2005 6:28 PM Subject: RE: Extending RequestProcessor to handle validation errors > On Wed, February 2, 2005 1:10 pm, Joe Germuska said: > > This actually stimulated another thought. Perhaps instead of > > overriding process validate, you could arrange to have your > > ActionMappings dynamically instantiated with the correct value for > > "input" (assuming that you can know it before you do the validation.) > > Actually, now you've stimulated a though in me! :) > > Correct me if I'm wrong, but processPreprocess() fires BEFORE processValidate(), correct? In that case, since I can in fact determine the input after processPreprocess() fires, I can simply call setInput() on the mapping with the new value, and everything should work as expected. > > Sound about right to you Joe? > > > I still think using the ComposableRequestProcessor is an easier solution! > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
