Hi Adrian Your right I didnt look at the spec as stated. But I did read up on transaction usage in general.
Most of the tutorials stated rollback would be deferred until the completion of the method that started the transaction. As the function name 'setRollbackOnly' I initially thought implied. These were obviously not JBoss specific resources but from Sun and IBM which I know doesnt neccessarily mean they apply to JBoss. I'm not saying the JBoss container is behaving incorrectly since the spec states it isnt. I just thought it made sense for the container to defer its rollback to the end of the method invocation. Especially in my situation where it means I can mark the transaction for rollback deep within my business rules, rather than by the service endpoint. Just a thought but this behaviour may help other developers with the task of migrating from other containers that do implement this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3905386#3905386 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3905386 ------------------------------------------------------- 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
