Our workaround is to switch to LockModeType.READ which translates to LockMode.UPGRADE (which works)
I suppose the LockModeType.WRITE -> LockMode.FORCE thing is just a plain old bug? (since hibernate 3.1 AND 3.2CR1 both don't actually support FORCE, same issue in the static map) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3940813#3940813 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3940813 ------------------------------------------------------- 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
