Message Title

Hardy Ferentschik commented on an issue

From a spec point of view this can only be addressed in an upcoming version of Bean Validation (1.2 or even 2). There is, however, already a related issue in Hibernate Validator (HV-819) which will make this available as provider specific solution.

Needs a thought regarding backwards compatibility of course.

Add Comment

Bean Validation /

BVAL-467

It would be nice to bring support of JDK8's Optional class.

Before JDK8, using Guava Optional class doesn't go very well with bean validation while I guess the user should be able to make the choice of using null values + @NotNull, or using Optional<Value>, but still be able to validate the non-null value

I guess it is a bit related to this:
https:...

This message was sent by Atlassian JIRA