On 9/3/07, Brian McCallister <[EMAIL PROTECTED]> wrote: > > On Sep 3, 2007, at 5:50 AM, James Strachan wrote: > > >> * Async exchange handling should always be assumed. > > > > I'm not totally sure about this one. One of the reasons JBI is so > > complex to work with is that it assumes all the hard stuff is always > > the case. e.g. if you want to use transactions, being async is a major > > nightmare. One of the major reasons why declarative transactions in > > spring are so easy to use is that it assumes a single threaded, > > synchronous programming model like servlets / EJB3 which simplifies > > the developers job tremendously. > > Asyc handling should be assumed because you don't know if it will be > synchronous or asynchronous with regard to a given component. Control > of that is outside the developers hands. >
Hi Brian, 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? -- Regards, Hiram Blog: http://hiramchirino.com
