Here is a simple example showing this is broken!
Take the Struts2 blank app for 2.0.11.1. Now add a simple Model Driven Action
with a model that has an Integer property testNumber. Now add a jsp with a
field testNumber. Now put fred in testNumber and submit.
You get Invalid field value for field "number".
Now replace the lib files from the 2.0.11.1 struts2 blank with the 2.0.12.
The Conversion errors now do not get displayed. They are lost!
--- On Mon, 10/27/08, David Harland <[EMAIL PROTECTED]> wrote:
> From: David Harland <[EMAIL PROTECTED]>
> Subject: struts 2.0.12 ParametersInterceptor Conversion errors lost
> To: "struts" <user@struts.apache.org>
> Date: Monday, October 27, 2008, 3:36 PM
> Hi,
>
> Since upgrading to struts 2.0.12 from 2.0.11.1 all
> conversion errors are bing lost.
>
> We have a date convertor for all Date fields. We have this
> convertor configured in the xwork-conversion.properties.
>
> Since we upgraded to 2.0.12 if you were to enter something
> such as 'fred' into a date field the value
> 'fred' is now being totally lost and the error
> message invalid.fieldvalue.startdate is not being displayed.
>
> It appears to be the ParametersInterceptor is taking a copy
> of the ValueStack, the conversion errors are being set on
> the new stack and therefore lost.
>
> Regards
>
> David.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
