Hi,
So just a thought. Why can't this be accomplished today with a
ParamConverter and a custom annotation?
Looking at the samples repo -
https://github.com/javaee-samples/javaee7-samples/blob/master/jaxrs/paramconverter/src/main/java/org/javaee7/jaxrs/paramconverter/MyConverterProvider.java#L18
I have to say that I don't understand your objection (in my defense: here
is almost 1:00 AM... :-) ), could you please clarify?
Probably the best solution will be to have a kinda
MultipleParamConverter interface in JAX-RS 2.1 specs defining two
methods:
T fromStrings(String[] values);
String[]
I can't agree to this. So a user registering a custom List provider
breaks the runtime ensuring the service code sees all the multiple values.
I can try and work with spec leads on clarifying it for JAX-RS 2.1.
Thanks, Sergey
On 23/10/16 23:27, Diego Ruotolo wrote:
Hi,
- when using
Hi,
- when using multiple-value parameters passed in the URI in an HTTP
>> compliant-way (PARAM=V1=V2=V3), the ParamConverter takes only
>> the first value, hence if the ParamConverter builds a list, it will be a
>> list of only one value
>>
>
> Are you saying this loses V2 & V3 ?
>
Yes, in this
Hi
Thanks for this investigation
On 23/10/16 22:57, Diego Ruotolo wrote:
Hi,
I investigated the behaviour of Jersey, and it acts like following.
Use case: a resource method that has a List as query parameter
- the method getConverter() of ParamConverterProvider interfaces receives
as
Hi,
I investigated the behaviour of Jersey, and it acts like following.
Use case: a resource method that has a List as query parameter
- the method getConverter() of ParamConverterProvider interfaces receives
as arguments: List as rawType, List as type, @QueryParameter as
annotations
- the
