Github user theigl commented on the issue:
https://github.com/apache/wicket/pull/246
@svenmeier: This makes a lot of sense. I'm not sure however how much time
I'll find the next weeks to work on this.
I suggest the following approach:
1. I'll look into this this week and try to rework the code as you
suggested.
2. If It takes too much time and I can't finish it, I vote for merging a
very simple version of this PR that only applies the changes required for
making `wicket-bean-validation` work with BV 2.0. I'll remove the API changes I
introduced in `BeanValidationConfiguration` and hard-code the list of built-in
annotations that imply a not-null constraint. This way, we do not introduce any
new methods that we would later remove if your solution is implemented.
WDYT?
---
