Yes, wrapping is an option but the code creating and closing the resource are probably not colocated.
I just looked at the UnitOfWork and it seems to be right on. It seems to be related to the AsyncCallback concepts. The done status on an exchange would have to be supported at the Exchange level to pull this off. So I guess I'll wait for James to finish this off. gnodet wrote: > > For streams, one way would be to wrap the stream and do some > processing when the stream is actually closed. In a general case, > James had introduced the concept of UnitOfWork on the exchange, but > the implementation is not finished. It seems as if you're looking > for the concept of the done status in JBI. > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > > -- View this message in context: http://www.nabble.com/Callback-on-Exchange-for-closing-out-streams%2C-result-set-cursors-tf4549498s22882.html#a13001281 Sent from the Camel - Development mailing list archive at Nabble.com.
