Implementation of interceptor chains / Flows / Camel / Listeners

[dwolz <di...@sopera.de>]

In
http://soatechlab.blogspot.com/2008/09/whats-new-in-servicemix-4x.html
http://soatechlab.blogspot.com/2008/09/whats-new-in-servicemix-4x.html 
I found the following statement:
"SMX3 has 4 flow types that ended up causing confusion and added complexity
for developers. This was simplified in SMX4 with a tendency to use explicit
routes by exploiting Camel's routing capabilities"
Please could someone explain what this means exactly?
In which cases should we use in SMX4
a) Flows
b) MessageExchangeListener
c) Camel
Will flows be supported in the future?
Which parts of the MessageExchange can be modified by a 
MessageExchangeListener?
Should interceptor-chain like applications (validation,
transformation,security-aspects,..)
better be implemented inside the NMR using flows or MessageExchangeListener,
or 
should they better be implemented as SE using Camel?
Exist examples for Camel based implementations of the SMX3 flow types?
-- 
View this message in context: http://www.nabble.com/Implementation-of-interceptor-chains---Flows---Camel---Listeners-tp19611598p19611598.html
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.