[
https://issues.apache.org/jira/browse/CXF-6623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Veit Guna updated CXF-6623:
---------------------------
Description:
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.
It seems that nested _@BeanParam_'s doesn't seem to be supported, since using
them does not have any affect.
Having (pseudocode):
{code}
class A {
@BeanParam
B b;
set(B b);
B get();
}
class B {
@QueryParam("foo")
String bar;
set(String bar);
String get();
}
Interface {
@BeanParam
something(A a);
}
{code}
Invoking Jersey's endpoint manually giving the query params seem to
work without a problem.
So it would be great, if this would be supported on CXF client side as well.
was:
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.
It seems that nested {code}@BeanParam{code}'s doesn't seem to be supported,
since using them does not have any affect.
Having (pseudocode):
{code}
class A {
B b;
@BeanParam
set(B b);
B get();
}
class B {
String bar;
@QueryParam("foo")
set(String bar);
String get();
}
Interface {
something(@BeanParam A a);
}
{code}
Invoking Jersey's endpoint manually giving the query params seem to
work without a problem.
So it would be great, if this would be supported on CXF client side as well.
> Add support for nested @BeanParam's
> -----------------------------------
>
> Key: CXF-6623
> URL: https://issues.apache.org/jira/browse/CXF-6623
> Project: CXF
> Issue Type: Improvement
> Components: JAX-RS
> Affects Versions: 3.0.4
> Environment: CXF JAX-RS client proxy, JDK8, Windows 7 64bit
> Reporter: Veit Guna
>
> 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.
> It seems that nested _@BeanParam_'s doesn't seem to be supported, since using
> them does not have any affect.
> Having (pseudocode):
> {code}
> class A {
> @BeanParam
> B b;
> set(B b);
> B get();
> }
> class B {
> @QueryParam("foo")
> String bar;
> set(String bar);
> String get();
> }
> Interface {
> @BeanParam
> something(A a);
> }
> {code}
> Invoking Jersey's endpoint manually giving the query params seem to
> work without a problem.
> So it would be great, if this would be supported on CXF client side as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
