Hi,
We can transform the XML format using XSLT. Likewise is there a way to
transform JSON format?
--
View this message in context:
http://camel.465427.n5.nabble.com/Message-Transformation-for-JSON-tp5744433.html
Sent from the Camel - Users mailing list archive at Nabble.com.
hm, I noticed that sometimes camel starts to consume messages in multiple
threads, 2 or 3 (I set 10 concurrent consumers), but more often in 1. it
seems there is not enough time to init consumers pool before route starts. I
add an asyncDelayed of 1 second to the route and now it works correct, but
Hi there,
Can you please clarify the source and target data format.
On Mon, Dec 9, 2013 at 3:12 AM, madusanka madusankabalasoor...@gmail.comwrote:
Hi,
We can transform the XML format using XSLT. Likewise is there a way to
transform JSON format?
--
View this message in context:
Hi,
source and target data formats are also JSON
--
View this message in context:
http://camel.465427.n5.nabble.com/Message-Transformation-for-JSON-tp5744433p5744490.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Can you double check if the message body can be converted rightly?
I think you can enable the trace[1] and check the log to see what is wrong.
[1]http://camel.apache.org/tracer.html
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
It’s dependence on do you want to hold the reference of client invocation proxy
and how do you prepare the request for invocation.
The processor way provides you a way to integrate the web service invocation
code within camel route, you need to take care of everything yourself.
You don’t need
You can use Spring to configure the CXF endpoint like this
beans xmlns=http://www.springframework.org/schema/beans;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:cxf=http://camel.apache.org/schema/cxf;