Jersey bean validation ParameterNameProvider

Question

I was reading the Jersey docs about bean validation. The ParameterNameProvider example shows how to define parameter names for a method. However, the implementation looks like this will have to be done for each and every method which obviously doesn't scale. The example is basically useless as is.

Is there a smarter way to do this? Couldn't Jersey infer the name from @QueryParam or @PathParam annotations?

score 3 · Accepted Answer · edited May 23 '17 at 12:00

3

Take a look at the answer in my question here. It should do exactly what you want.

Can I change the property path in a ConstraintValidator for Method arguments?

If you copy my code and run it through a debugger you will see that it is only evaluated once for each method for which it is used. Then during normal running of your app the names will not need to be resolved again.

edited May 23 '17 at 12:00

Community

1
1

answered Mar 22 '14 at 01:23

robert_difalco

4,821
4
36
58

I have a question: do the name parameters get cached somewhere or does that method get called for each exception? – Giovanni Botta Mar 24 '14 at 16:00
It gets cached when the class is first loaded. – robert_difalco Mar 24 '14 at 16:30
Actually I tested it and it does not. I simply printed a statement with the method name and it gets called as many time as the endpoint throws a validation exception. Adding caching with Guava's `Multimap` was easy though. – Giovanni Botta Mar 24 '14 at 16:38
I wonder if it's because of the particular implementation of the `MetaDataProvider`? – Giovanni Botta Mar 24 '14 at 16:44

Jersey bean validation ParameterNameProvider

1 Answers1

Linked