Hi Sergey,
Thanks for your reply.
On 29 Apr 2010, at 13:07, Sergey Beryozkin wrote:
> here '/s;s2' is a single 's' path segment, s2 is a matrix parameter.
> '/s;s2=1;s2=2' is a single 's' path segment with two identically
> named matrix parameters, so you can catch all the 's2' matrix parameters
> using @MatrixParam("s2") List<String>, using @Path("/s1") only - is it what
Makes sense.
> you'd like to do ? Alernatively, you can try to use @PathSegment("s")
> parameter and get all the matrix parameters from it, or you can have a
I'll try that. I missed that annotation.
> At the moment, proxy-based clients do not really understand well how to deal
> with collections - some enhancements will need to be done. You may find it
> easier for now to use WebClients. Altermatively, if what you'd actually like
> to use is matrix parameters then you might want consider introducing some
> MatrixBean with a List<String> s2 propert and use "@MatrixParam("")
> MatrixBean" in your method signature, which will make it possible to use
> proxies too
I suspected as much. I'll try using a MatrixBean. If I fail I can fall back to
a WebClient as you suggest.
> I think it won't do it for Lists given that support for
> collections(lists/sets) of named (path/query/matrix) paramers is required by
> the spec but I think if you had say List<Foo> and also registered
> ParameterHandler<Foo> then you'd see it called...
Ah. That explains it.
Thanks again,
Matt
>
> thanks, Sergey
>
>
>> Thanks very much for your time,
>>
>>
>> Matt
>>
>>
>> Matthew Glubb
>> Technical Partner
>>
>> email: [email protected]
>> phone: 44 (0) 7715 754017
>> skype: mglubb
>>
>> Kite
>> http://madebykite.com
>>
>> --
>> GPG: 96FF DE0E 0B7B 37F0 7F8D C54C E285 3D8F 5625 9244
>>
>>
