He's not using SEMPPL + his own TX management. He's using his own TX management despite SEMPPL.
He only moved away from SEMPPL to his own TX management when he could not resolve the exception previously mentioned in this thread: "could not register synchronization with JTA TransactionManager", caused by "Already marked for rollback TransactionImpl". We've got code that's been running fine for 6 months on Seam beta 1 + JBoss 4.0.3. Now with the upgrade we're hitting this exception. I wish whatever code was marking the transaction as rolledback would throw an exception as it's rolling it back. I've been working at this for days without making any progress. Going back to Seam beta 1 and Jboss 4.0.3 hardly seems like a solution. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3940191#3940191 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3940191 ------------------------------------------------------- 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
