+1 on the idea that stuff like @Length(min=3) triggers a validation error although required=true is missing if the field is empty! Is there an actual reason that this isn't the way it behaves? For the people who want custom validation messages for certain input fields: http://www.oracle.com/technology/pub/articles/masterj2ee/j2ee_wk7.html (the "Adding Meaningful Field References" section) describes a way doing this by using a PhaseListener that customizes the validation messages based on parameter supplied by f:attribute tags inside the h:input stuff. Does anyone now if the above approach is performance expensive? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4006533#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...