Correct, that is all I need to do for that test case. There are lots of other @Constraint's and lots of components in both Swing and SWT. That makes a pretty large matrix to implement. I want all of the user interface programmers on my project to use the bean validator. Making it simple for them to do is important, or they just won't do it. The existing bean validator implementations already do the hard part, I was just trying to make using them easy in a different context.