Just wondering if this behavoir is expected or not. It has bitten me again. I thought I had a fairly decent understanding of Conversion and Validation - maybe I don't :-).
Converters for javax.faces.Boolean, Byte, Character, Double, Integer Long, Short are automaically used for primitive and their wrapper types. If you don't specifically state validation (e.g. required="true" or <f:validate*/>) then no validation occurs. However, I'm getting "Validation" errors when no validation is set. Moreover, the errors seem to be Conversion in nature because of type incompatablilty (see original thread). But there really is no type incompatability thanks to the auto converters... Am I seeing this clearly? John Ruffin wrote: > > I may have missed this tidbit but in 1.1.5 it appears that UI value > bindings have to be bound to objects of type String and then converted to > whatever you want it to be (Character, Integer, etc...) - else you get > validation errors (e.g. Validation Error "leadTimeLevel": Value is not a > valid option.). > > Above, leadTimeLevel is type Integer in my database, hibernate mappings, > POJO, etc... However, I can't bind an outputText directly to it or I'll > get the Validation error. > > I have to create a new String in the bean, bind the outputText to the new > String, then in my listener (before I save) I have to setLeadTimeLevel(new > Integer(stringICreated); > > This happened when I switched from 1.1.4 SNAPSHOT to 1.1.5 SNAPSHOT (api, > impl, tomahawk, sandbox). > > I hope this is a bug. Can someone elaborate? > -- View this message in context: http://www.nabble.com/Snapshot1.1.5-and-Validation-tf2482064.html#a6953074 Sent from the MyFaces - Users mailing list archive at Nabble.com.
