Just delaying the rollback to the end of a method seems of little use in the general case of an arbitrarly deep stack. I would also argue that propagation of the ejb context and its setRollbackOnly method to the business layer is an improper propagation of a concern (transactions) that should only be dealt with at the ejb facade layer.
In general, these "lack of portability" issues should be raised to the corresponding j2ee spec mailing list as feedback to the effectiveness of the specs definition of semantics. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3905552#3905552 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3905552 ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
