Hi,

Is there a case for adding an echo() processor to the fluent DSL, where the
echo() processor simply copies the In message to the Out message? This could
be useful for capping off routes that process InOut exchanges. For example:


from("jetty:http://FooHost/Bar";)
  .process(...).process(...)
  .to("cxf:bean:MyService")
  .process(...).process(...)
  .echo();

Where this example wraps a CXF Web service endpoint. The first couple of
processors, process(..), do work on the Web service _request_, and the
processors that come after to(...) do work on the Web service _reply_. At
the end of the route, you need to reflect the the reply back to the JETTY
endpoint. An echo() processor would be handy for this purpose.

I realize that this is not tremendously critical, because you could already
use 'transform(body())' to achieve the same effect. But using an echo()
processor is possibly more elegant.

-
Fintan
-- 
View this message in context: 
http://www.nabble.com/echo%28%29-processor-tp19086322s22882p19086322.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to