So, are we talking of "real" clients, that read some data, display it to the user, and after 20 minutes the user commits new data?
Then it is really no good practice to keep the entity-reference on the client (with a transaction open ?!!) - the client should never ever have direct access to an entity bean. instead, implement some VO-Pattern here. To avoid the situation "last one wins", i would just manually keep locking information somewhere that says "another using is editing this data, please try again later". (simply create a table with user/pk information or use a synchronized singleton) By the way, if you have the entity-reference on the client: client2 will not even be allowed to read the data if client 1 has placed a lock on it (open transaction, default behaviour), so client2 can not even display the data. summary: do not use entity beans to synchronize client interfaces! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3844106#3844106 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3844106 ------------------------------------------------------- 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
