Looking at the start page of http://beanvalidation.org/ left me puzzled. I thought @Email wasn't part of BV, neither 1.0 nor 1.1 - and indeed it isn't (pity).

I found a thread from 2009 that discussed its potential inclusion: https://forum.hibernate.org/viewtopic.php?f=26&t=993681&start=0&hilit=email

I believe the most prominent BV code sample on the official website shouldn't feature an annotation that isn't part of the spec.

I'm also confused. But more about the example itself:
currently it looks like:
public void createUser(@Email email, @NotNull String name) {}
in my opinion it should be:
public void createUser(@Email String email, @NotNull String name) {}

Maybe I'm simply wrong and I don’t understand this example.

Yep, that's correct.

I've fixed the example on beanvalidation.org; Thanks for the pointer!

Regarding the usage of @Email: It's one of Bean Validation's core features to allow for the implementation of custom constraints so it makes sense to show-case this in the example.

Hibernate Validator - the BV reference implementation - comes with an @Email constraint, which btw. is surprisingly hard to get right as different definitions for a valid e-mail address apply in different contexts. E.g. "bob" might be a valid e-mail address on localhost, but typically that's not what one wants when validating input representing e-mail addresses. Also allowed length for the domain and name part are not 100% clearly defined either as different RFCs apply.

--Gunnar

Thanks for fixing the sample.

I was neither criticizing the fact that @Email is included in the sample nor that it isn't part of the spec. I fully understand why it can't be in the spec but I still wish the circumstances were such that it'd be feasible to include it...

However, I'd still appreciate if the code sample would make it very clear that @Email isn't part of BV but a Hibernate extension.