Are you using direct JDBC or a OO data technology like EJB3 or Hibernate? Hibernate does have object locking and you could probably use that. As for users that leave without logging out, you could implement a standard servlet session listener and listen for session expirations and unlock any objects at that time.
On 10/29/07, ULA UVULA <[EMAIL PROTECTED]> wrote: > Hi, I'm a newbie. > Can somebody can give me a hint? > > I have written a jsf application which is maintaining a java data structure > (bean). (BTW: I never have written any jsp pages, I direct > starting with jsf). > > Is there any way to inform the users that another user is already > manipulating this structure? > > Workflow: > a user can add/delete/edit/copy items into the data structure. After the work > is finished, the user can > "activate/save" his settings. During this time span, I want to lock the page > for other users or at least I want to > inform the second user, that another user is already active. > The goal is to have consistency and not "last write wins". > > Can you also consider: what happens, if the first user is closing the > web-browser without doing a "logoff" on the page? > > Thanks > Uvula > > > -- > This mailbox is not official and not checked regular. It's only > a workaround to have access through the web. > > Please also reply to [EMAIL PROTECTED] > Uwe Langjahr / HP Service Consulting & Integration > > > > Psssst! Schon vom neuen GMX MultiMessenger gehört? > Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger >
