Since the data in Table1 effectively doesn't exist until the COMMIT, this is not going to work. Transaction isolation levels will prevent this regardless of whether or not they are in the same transactions.
Do you actually want to implement something like this, or is this just a test scenario for you? Easiest solution would be the demarcate each EJB method with boundaries such as REQUIRES_NEW. Let the first transaction complete and then insert the second value. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956331#3956331 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956331 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 JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
