How are any of you solving the problem in the stateless webapp context where
two users pull up the same record from a database in a JSP page, and user
one changes the address and saves but then user two, who has the old address
on his JSP page, changes the phone number and hence over-writes user one's
address change? Are you locking the record in the back-end database and then
implementing the SessionBindingListener to release it when the session
expires, if the user leaves the webapp without logging out? Does EJB solve
this problem? I'd like to hear the solutions that are out there.
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
