On Sep 7, 2007, at 2:45 PM, Brian McCallister wrote:
Just to clarify your saying that the core components / processors
should invoke other processors using the async API, not to cause
async
processing to start occuring, but to handle the case where the
invoked component does complete the processing async. Correct?
Yes. Personally, I think there should not be separate APIs and
transactions shouldn't span component boundaries...
To expand on this -- any well written component needs to operate
correctly under sync or async conditions. As such, Camel should
expose a single API which handles the difference underneath.
-Brian