Thanks Willem for your response.
I have another question, can we design an application service with Camel to
have a mini state managed workflow. For example, we receive an webservice
request from consumer which needs to be asynchronously processed. The
asynchronous processing can involve invocatio
Hi Subbu,
Processor is basic build block of Camel route, each route has bunch of chained
processors to do the EIP work. When you add a processor, camel will add trace,
error handler interceptors to wrap the processor for you. These interceptor
just add some method call stack, and it doesn't cos
Thanks Christian for your response.
But my question was do we have any implication if we write too many
processor to a given request.
The way we have written our application is we have exposed a webservice and
we have number of processor in a route to process the request..
The question is more
If the request is SOAP based and you validate the request against an XML
schema, CXF can already do that. No processor needed for this requirement.
To transform between different types/objects, I recommend to use the Camel
TypeConverter mechanism [1] and implement your own type converters. No
proce
Does anyone have an answer. Please reply it will be very helpful.
Thanks & Regards,
Subbu.
--
View this message in context:
http://camel.465427.n5.nabble.com/Best-Practice-to-write-Processor-tp5756514p5756554.html
Sent from the Camel Development mailing list archive at Nabble.com.
