Offer helper classes to build ConstraintViolationExceptions (and potentially raise them)

Description

New convenience methods on Validator: void assertValid(Object o)/assertValidProperty(...)/assertValidValue(...) which throw a runtime ValidationException

90% of the time we want to do:

From http://docs.jboss.org/hibernate/stable/validator/reference/en/html_single/#validator-usingvalidator-validate

So why not supply a facade method to make it easy for us developers (especially those migrating from hibernate validator 3)?

That allows the bean validation to standarize the Exception too:
a ValidationException (or InvalidStateException or whatever you call it), which is of course a runtime exception.
That in turn, allows the front-end frameworks to deal with that exception more cleanly (give the user a clue why the business method failed when it imported that address without a street from an import addresses file).

Give special care to the message of that exception. It should clearly state at least 1 of the validations that failed (in english, not i18n)
so when we find such an exception in the log we can easily see what caused it.

Environment

None

Assignee

Unassigned

Reporter

Geoffrey De Smet

Labels

Feedback Requested

None

Feedback Requested By

None

backPortable

None

Suitable for new contributors

None

Pull Request

None

backportDecision

None

backportReEvaluate

None

Components

Fix versions

Affects versions

Priority

Minor
Configure