Any chance of getting ClassValidator to validate EJB3 annotations in addition to the Hibernate validation-specific annotations?

So for example if you annotate a field with @Column( nullable = false ), it validates the same as if you annotated it with @NotNull. I'm in the middle of adding validation to all my domain objects, and my DRY radar is going nuts...

Do it the other way around


will create a not null column

As a rule of thumb, I find it best to follow the standard, when one exists. I know that Hibernate's @NotNull existed before @Column, but if Hibernate bills itself as the premiere JPA implementation, I would think that it makes sense to consider the @Column's nullable value. (I would be concerned that some future JPA tools may pay attention to @Column, and ignore non-standard annotations like @NotNull.)

Back to the original question, "Why can't ClassValidator validate EJB3 annotations in addition to the Hibernate validation-specific annotations?"

because when using a mix of ORM.xml and annotations, you are stuck