anonymous wrote : Also, the transactionManagement property in @Consumer (as described in the wiki) seems to have disappeared.
I was beginning to wonder that exactly. All of my tests have shown that transactions are not maintained regardless of the connectionFactory used. Removal of transactions is a show stopper for my group. It would be nice to have this. Even if it presupposes synchronous behavior, I feel as though this is okay because it allows us to provide a decoupled application at least. In this way we can allow concerns to be clearly defined. We strive to ensure that there is no concern leakage. However, if there is no transaction support, we'll have to bleed some of the concerns into other parts of the application. This is unfortunate. I still see JBoss' mdps as a great step forward, just not 100% what we had hoped for. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3926390#3926390 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3926390 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
