No offence, I think Hibernate validator is one great product. But does it need to be tightly integrated with Seam 2.0? Since in org.jboss.seam.core.validators, it's @Install(precedence=BUILT_IN) The issue is if user chooses not to use Hibernate as the persistence strategy or Hibernate validator also if that library is not bundled in the appserver such as glassfish. I know it's just a matter of adding hibernate-validator.jar in the classpath. But again if user doesn't use it, won't it just be useless? Will it be better if the precedence is not BUILT_IN? Or are there other thoughts regarding this? Just my two cents View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4061807#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...