Right, but SEMPPL does tx management. In fact, that is *all* it does. If you want to do your own tx management, you don't need it.
anonymous wrote : I wish whatever code was marking the transaction as rolledback would throw an exception as it's rolling it back The only things that call setRollbackOnly are the EJB container (as defined by the spec), the EM (as defined by the spec) and the RollbackInterceptor (for JavaBean components). This only happens as an exception is propagating out of one of them, so there is no way that setRollbackOnly() is ever called w/o an exception propagation. So unless either the application or JSF is swallowing exceptions, there _is_ an exception. The only problem here is the known bug where EJB3 and Hibernate try to register synchronizations on a tx marked for rollback. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3940195#3940195 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3940195 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
