camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Subbu <>
Subject Best Practice to write Processor
Date Mon, 15 Sep 2014 04:38:58 GMT
Hello All,

Currently in my application we are defining a Processor for a particular
functionality to be achieved. 

For example, we have a webservice based service, we are using CXF to expose
a webservice the endpoint.

At the start of the route, the "camel:from" is configured as the webservice
endpoint, then followed a Processor for RequestValidation then followed by
Processors. This service which we are  developing is more of integration
between multiple services, so after the RequestValidation, there is a
Processor to construct the Request to be sent to DownStream System and
invoke of downstream service using cxf client, then there is another
Processor created for handling the response and constructing the response
and return to calling client of our service.

So, if you consider an operation in our service we have some 3 or 4
processor written for a specific route.

Can someone tell me whether this is good approach to write a Processor to
fulfill a given functionality or is it better to consider a Camel Processor
in parlance with Struts Action classes. Where we receive the request and
hand it over to a business delegate, which then taken returns the final
response to be send to the GUI.

Thanks & Warm Regards,

View this message in context:
Sent from the Camel Development mailing list archive at

View raw message