In my experience it's better to define number (and time) input fields as String and perform the conversion and validation in your action using java.text.NumberFormat . This puts you in control of the process and let's you handle I18N issues that way you want to without fighting Struts.
I typically have a couple of helper methods I put into the base Action class that simplify getting the users Locale and NumberFormat. Depending on the app the users Locale may come from a Login object or the browser request (which Struts can retrieve) or from a cookie. On Tue, Mar 30, 2010 at 5:56 AM, Juanjo C <jjcuadr...@gmail.com> wrote: > Any idea? > > 2007/10/23 Pedro Herrera <pedro_herr...@hotmail.com> > >> >> Hi, >> I have a currency input field (BigDecimal). In my location the decimal >> point is comma, eg, 10,00(==10.00) must be permitted. Struts is throwing a >> message error : Invalid field value for field "valor". >> >> >> Thanks >> >> Herrera >> >> >> -- >> View this message in context: >> http://www.nabble.com/-s2--number-format-s%3Atextfield-tag-tf4680318.html#a13373598 >> Sent from the Struts - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: user-unsubscr...@struts.apache.org >> For additional commands, e-mail: user-h...@struts.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org