As you propose, you can use an annotation to provide that information @Named(“MyParameter”) and then check for the presence of that annotation during the aspect execution (but at it’s current state bval won’t use it when creating the constraint violations).

You can also define specific error messages for each parameter, but that’s probably too verbose.

You should hit apache’s bval jira to see if we can work on something better, as for example knowing the cardinality of the parameter (so for example the constraint violation will indicate that the 2nd argument in your methodcall(string,int) failed) is something worth implementing. https://issues.apache.org/jira/browse/BVAL

I am using method validation as you proposed for a current project and it is very useful.

There’s just a small – but important – problem: The returned constraint violations do not contain any useful information in their property path. What can I do to identify the parameter which violated its constraint(s), or is it even possible to get its name? For example, could I add an annotation to the parameters specifying a name / property path to use for regarding violations?

Thanks
Chris