I am not sure if this is something worth mentioning. But the latest API changes to the FacesMessages might cause unexpected form validation behavior for people who are migrating from 1.1.6. With 1.1.6, I used the method FacesMessages.add(String id, String messageTemplate, Object... params) to associate a validation error message with a UI component. Now with 1.1.7 the same method will map to FacesMessages.add(String messageTemplate, Object... params) which will add the component id string as a global message and therefore prevents the validation system from detecting that the UI component has a validation error. The solution, of course, is to use addToControl(String id, String messageTemplate, Object... params) instead. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022210#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...