Thanks for the responses. I feel a little more confident that there isn't something magical already out there to handle this particular problem domain. I do want pessimistic locking as I want to inform the user that someone else is already thinking and in progress of changing something BEFORE they try to change it themselves, and it is very possible for two peeps to attempt edit on the same item. I am also using mySQL not Oracle and wouldn't probably want to rely on a database specific implementation if I could avoid it. As of now, I have created a lock table in memory at the app layer and it sounds like a reasonable approach based on my query from fellow colleges on this forum -- Steve -- View this message in context: http://www.nabble.com/Dirty-read-edit-problem.-tp24157057p24167367.html Sent from the Wicket - User mailing list archive at Nabble.com.
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
