WICKET-6656 bean validation handle required annotations#353
Closed
WICKET-6656 bean validation handle required annotations#353
Conversation
added 2 commits
April 19, 2019 20:22
solomax
approved these changes
Apr 21, 2019
bitstorm
pushed a commit
to bitstorm/wicket
that referenced
this pull request
Apr 24, 2019
and updated dependencies; this closes apache#353
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Let BeanValidationContext decide which annotations make a component required.
This way projects can choose to let beans-validation check those annotations instead, see BeanValidationApplication as example.
To make this possible, PropertyValidator accepts nulls now.