The ejb spec does not indicate whether or not any additional work can be performed in the essentially invalidate transaction, but its somehwat implied that once setRollbackOnly is called the business method work should be completed:
anonymous wrote : | 17.3.4.2 javax.ejb.EJBContext.setRollbackOnly Method | An enterprise bean with container-managed transaction demarcation can use the setRollbackOnly | method of its EJBContext object to mark the transaction such that the transaction can never commit. | Typically, an enterprise bean marks a transaction for rollback to protect data integrity before throwing | an application exception, because application exceptions do not automatically cause the container to | rollback the transaction. | Why isn't the rollback done after accessing bean? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3904931#3904931 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3904931 ------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
