I need this behaviour because I wanna avoid this situation: CLIENT 1 starts modifying some data: it reads data, updates them (using a GUI) and writes them in the DB.
if CLIENT 2 starts after CLIENT 1's start, but before CLIENT 1's update, it can try to write in DB "no more valid" data I prefer that CLIENT 2 is not allowed to start if there is another transaction that is managing the same data. Hi, Moreno View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3844099#3844099 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3844099 ------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
