The message is:
form_solicitud:monto_solicitado: 'asd' must be a number consisting of one or more digits.
The thing here is that I do not use error.properties or similar generic validation overrides, just custom validators set implicitly to be able to denote every field failing by its form description and not ugly limited id.
The bean property IS of java.lang.Double type as I mentioned before.
As for the converter I didn't have time to come to this part yet but I will. Still the input should be validated before it's converted or the convertor will fail. The actual problem is that the validation used in my case never gets to my custom validator and thats what worries me. And it's even worse - the field is always validated even if I leave it with the
value attribute only. I don't believe I can't just set a field for a Double bean property without it being always validated. I am not a beginner in JSF and I though I control who gets validated and who doesn't...
One interesting fact btw. Some time ago I tried
EJB bean validation using annotations from hibernate validation lib. It didn't work as I expected and I deleted all the changes as well as the lib, cleaned the project and redeployed it. And that's why I call it freakin magic: the validation from the EJB was there... Well, it's difficult to surprise me, so I completely cleaned and rebuilt the project, reinstalled the server from scratch, rebooted the pc (since RAM and cache act like a damn parallel universe sometimes) launched the app, and what do you think - the bean validation was still there. The field I was experimenting with was this and very same one I'm having problems right now...
A few more days with this thing and I will dedicate the rest of my life to the ancient maya gods.
Wanna install linux on a vacuum cleaner. Could anyone tell me which distro sucks better?
willCodeForFood("Java,PHP,C#,XML,VBS,XHTML,CSS,JavaScript,SQL"); //always looking for job opportunities in AU/NZ/US/CA/Europe :P