if the log line bother you but not the transaction just configure logs to not write it.
about mdb/async: if async is needed you dont need the overhead introduced by JMS/AMQ (serialization...) *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/3/23 Howard W. Smith, Jr. <[email protected]> > On Sat, Mar 23, 2013 at 5:23 PM, Romain Manni-Bucau > <[email protected]>wrote: > > > well about logs it should jus tbe configured but will not prevent tx to > be > > handled ;) > > > > Not understood. > > > > > > @Async is great and you can handle after return part usnig AsyncResult. > > > > > Understood. I have some code in place that is ready to use. I stopped using > it, but I may revisit. I think I remember seeing you recommend > @Asynchronous (over MDB/JMS) some time ago, and i definitely saw David > Blevins with a nice code example on stackoverflow.com; that is what really > motivated me to use/add that to my web app. > > I am so pleased with tomee 'simple MDB', i may not even try to use @Async. > we'll see. :) >
