I think you can't have more than 1 resource class to create a right proxy as
i have investigated the code and CxfRsEndpoint only sets the first
resourceClasss upon setting up of JAXRSClientFactoryBean
Here:
protected void setupJAXRSClientFactoryBean(JAXRSClientFactoryBean cfb) {
I don't think current Spring DSL support to set the Object[] into
header. I'm afraid you need to use processor or Java DSL to do this job.
Willem
jejmaster wrote:
Hi Willem,
Thats another good feature. But how do you set the Object[] varValues on
CxfConstants.CAMEL_CXF_RS_VAR_VALUES message h
Hi Willem,
Thats another good feature. But how do you set the Object[] varValues on
CxfConstants.CAMEL_CXF_RS_VAR_VALUES message header via spring xml?
?
Or do I still need to create a processor bean class to manually set this?
Regards,
Jejo
willem.
Oh. my mistake.
If you take a look at the CxfRsProducer.invokeProxyClient(Exchange
exchange), you will find you need to set
CxfConstants.CAMEL_CXF_RS_VAR_VALUES message header to set the varValues
if there are more than one resource class to create a right proxy.
Willem
jejmaster wrote:
I s
I see. That's great. So you mean the serviceClass parameter is optional when
configuring cxf? How do you expose the service without specifying the
serviceClass ? Isn't it required configuring at least the cxf:rsServer?
http://localhost:8080/services/rest";
serviceClass="com.project.service.impl
It's hard to create the Proxy without specify the ResourceClass.
HttpClient API is more friendly, as you don't need to specify the
ResourceClass when creating the client.
Willem
jejmaster wrote:
Hi Willem,
Its working enough in 2.3-SNAPSHOT. but we decided to use 2.2 as of the
moment until 2
Hi Willem,
Its working enough in 2.3-SNAPSHOT. but we decided to use 2.2 as of the
moment until 2.3 gets released.
Do you recommend on the httpclient rather than the proxyClient?
Jejo
willem.jiang wrote:
>
> Hi Jejo
>
> Please feel free to log a JIRA for it, doesn't the HttpClient work g
Hi Jejo,
I just checked the code of CxfRsProducer, the parameter is taken from
the inMessageBody with Object[].class.
Maybe something is wrong with this part of code.
Can you attach a small test case into the JIRA? It will help us to find
a way to resolve this issue quickly.
Willem
jejmast
Hi Jejo
Please feel free to log a JIRA for it, doesn't the HttpClient work good
for you ?
Willem
jejmaster wrote:
I found out that JAXRS Client only sends 1 parameter. So i will just have to
configure my service class to only accept 1 parameter instead of two. Ill
just wrap it in a transfer
I found out that JAXRS Client only sends 1 parameter. So i will just have to
configure my service class to only accept 1 parameter instead of two. Ill
just wrap it in a transfer object.
Anyway, maybe as a enhancement to camel-cxf jaxrs, hopefully we can also use
and support different rest client
Hi Willem,
I just used the TestProcessor to see the value of the inMessage.getBody()
because even if there's no processor, the parameters really gets null when
routed.
I am digging the code right now at CxfRSProducer. And it seems that the
problem is in the Reflection part in the method invokePr
Hi,
Can I see the code that you do in the testProcessor?
If you don't set the exchange.outMessage(), you should get the right
parameter from the inMessage body.
Willem
jejmaster wrote:
Hello,
I am using the Camel 2.3-SNAPSHOT and implementing the CXFRS routing through
ProxyClient. I have s
12 matches
Mail list logo
