camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raghuveer <raghuveer.maga...@gmail.com>
Subject Exchange body - service client
Date Tue, 29 Mar 2016 16:32:30 GMT
We have different service clients like search client, update client, create
client etc. Each client is written as a bean (route). These clients will be
reused by multiple functionalities and also each functionality may call
multiple routes. I am looking for an better approach for setting the
exchange body. Using camel, in general it is better to have each client with
its own request and response like search request, search response etc..? Or
can we have one common object that can be pass as input and the service
response set to the same object so that object can be passed as input to
other service client? In the first approach we have to do transformation and
in second approach, no need to do the transformation. In general which is
better approach? Or is there any other better way of doing..?




--
View this message in context: http://camel.465427.n5.nabble.com/Exchange-body-service-client-tp5779983.html
Sent from the Camel Development mailing list archive at Nabble.com.

Mime
View raw message