…te() because of the lack of a return value
…essageTemplate() and getMessageParameters() Had to refactor the validation tests at the same time and fixed various small bugs while doing so.
…GlobalExecutionContext A new ExecutionContext is now created everytime that GraphWalker::walkConstraint() is launched. Because of this, a validator B launched from within a validator A can't break A anymore by changing the context. Because we have a new ExecutionContext for every constraint validation, there is no point in modifying its state anymore. Because of this it is now immutable.
…rror message is empty
… when group sequences are validated This conforms to JSR303 (see version 1.0 final, page 39).
The constraint "Valid" does not accept any options or groups anymore. As per JSR303 1.0 final, section 3.5.1 "Object graph validation" (page 39), properties annotated with valid should be cascaded independent of the current group (i.e. always). Thus the group "*" is not necessary anymore and was removed from the "Valid" constraint in the Form validation.xml.
…18n management should be done globally, not in a specific component)