Re: Aw: Re: @...Param and client proxy

r 2015 um 13:35 Uhr Von: "Sergey Beryozkin" An: users@cxf.apache.org Betreff: Re: @...Param and client proxy Hi Veit FYI, the nested BeanParams work OK now Re a client proxy restriction that if you set @BeanParam on a field, setter/getter is still needed. As I mentioned - this is not

Aw: Re: @...Param and client proxy

Hi Sergey.   Didn't find time yet to test it, but I'm confident that it will work :).   Thanks! Veit   Gesendet: Freitag, 09. Oktober 2015 um 13:35 Uhr Von: "Sergey Beryozkin" An: users@cxf.apache.org Betreff: Re: @...Param and client proxy Hi Veit FYI, the nested BeanPara

Re: @...Param and client proxy

Hi Veit FYI, the nested BeanParams work OK now Re a client proxy restriction that if you set @BeanParam on a field, setter/getter is still needed. As I mentioned - this is not needed on the server side, given that there are spec examples around of having the fields only, without method access

Re: @...Param and client proxy

On 04/10/15 18:44, Veit Guna wrote: Alright. Thanks for the quick feedback! May I create a ticket for that? Sure, please do open JIRA tickets whenever you spot CXF client issues Cheers, Sergey Thanks Veit Am 04.10.2015 um 19:33 schrieb Sergey Beryozkin: Hi Veit The client proxy code appa

Re: @...Param and client proxy

Alright. Thanks for the quick feedback! May I create a ticket for that? Thanks Veit Am 04.10.2015 um 19:33 schrieb Sergey Beryozkin: > Hi Veit > > The client proxy code apparently does not support nested BeanParams, > so more work will need to be done > > Cheers, Sergey > On 04/10/15 19:21, Veit

Re: @...Param and client proxy

Maybe https://code.google.com/p/reflections/ could help? 2015-10-04 19:18 GMT+02:00 Sergey Beryozkin : > Hi Veit > > The CXF server will also work the same way, the restriction is only on the > client proxy side, I've just checked a code, it should be sufficient to > have a setter - which is used

Re: @...Param and client proxy

Hi Veit The client proxy code apparently does not support nested BeanParams, so more work will need to be done Cheers, Sergey On 04/10/15 19:21, Veit Guna wrote: Hi Sergey. I see. Any news about the nested @BeanParam :)? Cheers Veit Am 04.10.2015 um 19:18 schrieb Sergey Beryozkin: Hi Veit

Re: @...Param and client proxy

Hi Sergey. I see. Any news about the nested @BeanParam :)? Cheers Veit Am 04.10.2015 um 19:18 schrieb Sergey Beryozkin: > Hi Veit > > The CXF server will also work the same way, the restriction is only on > the client proxy side, I've just checked a code, it should be > sufficient to have a sett

Re: @...Param and client proxy

Hi Veit The CXF server will also work the same way, the restriction is only on the client proxy side, I've just checked a code, it should be sufficient to have a setter - which is used to determine a possible field candidate without having to check all the fields - this is done on the proxy si

Re: @...Param and client proxy

While working around the nested @BeanParam for now, I encountered the fact, that @...Param annotations work on fields now, but somehow getter/setter for that field are still required. Leaving them out, will leave the value unset on request. On the opposite, the Jersey server is fine with fields wi

Re: @...Param and client proxy

Ok, 3.0.5 seems to fix the field annotation issue - nice :). One to go... Am 04.10.2015 um 10:13 schrieb Veit Guna: > Hi. > > I'm using Apache CXF 3.0.4 on client side against a Jersey based REST > service. > On client side I'm using the CXF client proxy using the server side > interface classes.

@...Param and client proxy

Hi. I'm using Apache CXF 3.0.4 on client side against a Jersey based REST service. On client side I'm using the CXF client proxy using the server side interface classes. Now I encountered, that annotated fields (e.g. with @QueryParam) on @BeanParam classes are ignored when invoking a method passi