Re: [hibernate-dev] null values in validation

> > Another thing we wondered about is the default behaviour of built-in > constraints when they validate null values. Are they supposed to succeed > on null values by default? That's a suggestion by the Bean Validation Specification. The spec says: "While not mandatory, it is considered a good practice to split the core constraint validation from the not null constraint validation (for example, an @Email constraint will return true on a null object, i.e. will not take care of the @NotNull validation) null can have multiple meanings but is commonly used to express that a value does not make sense, is not available or is simply unknown. Those constraints on the value are orthogonal in most cases to other constraints. For example a String, if present, must be an email but can be null. Separating both concerns is a good practice."