Not sure, but I think you should try something like this :
(InputStream) is = exchange.getIn().getBody();
Read the byte array into a string and then convert jsonstring to your
object.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-for-Rest-Service-tp5723267p5723311.h
read. Please help.
Thanks, Bala
From: Sergey Beryozkin-3 [via Camel]
To: Bala
Sent: Tuesday, 27 November 2012 3:33 PM
Subject: Re: Camel for Rest Service
On 27/11/12 07:56, Willem jiang wrote:
> What's invocation looks like, you should get a Re
Sorry, I Can't understand your reply. Can you please be more specific.
If you look at what am trying, I try to use the Configuration file for
invoking a uri and from the configuration file, am trying to call a rest
service, from which am getting the response in JSON which am trying to read.
Plea
On 27/11/12 07:56, Willem jiang wrote:
What's invocation looks like, you should get a Response object from the message
body.
If you are using camel-cxfrs you will not see the under layer response (XML or
JSON).
After upgrade to CXF 2.7.1 it will be possible to do
Response response = ...
MyT
s as below.
System.out.println("--->" + exchange.getIn().getHeaders().toString());
System.out.println("--->" + exchange.getIn().getBody());
Thanks
From: Willem.Jiang [via Camel]
To: Bala
Sent: Tuesday, 27 November 2012 1:27 PM
Subject:
n internet too.
>
> Thanks in advance
>
>
>
> From: Willem.Jiang [via Camel] (mailto:ml-node+s465427n5723270...@n5.nabble.com)>
> To: Bala mailto:vbal...@yahoo.co.in)>
> Sent: Tuesday, 27 November 2012 10:47 AM
> Subject: Re: Camel for Rest Service
>
>
too.
Thanks in advance
From: Willem.Jiang [via Camel]
To: Bala
Sent: Tuesday, 27 November 2012 10:47 AM
Subject: Re: Camel for Rest Service
If you are using the processor to handle the response message you need to take
the in message instead of take the out mes
If you are using the processor to handle the response message you need to take
the in message instead of take the out message.
As Camel Pipeline will copy the out message of previous exchange to the next
exchange in message.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web:
