Hi, Thanks for your quick response.
The scenario is same as given in the issue http://www.jboss.org/index.html?module=bb&op=viewtopic&t=57794. The reading and writing of data are happening in two different transactions. Hence the container takes what is there currently in the database(timestamp) and add the same in the where clause and the update suceeds without any issue. Our requirement is that we need the optimistic lock to be applied even when the read and writes are in 2 different transactions. Probably we need to do this check at our application level. Have a method in our EntityBean called checkConflicts which compares the version with the client and the one in the db. Is my understanding correct? If it is correct then in a web based enviroment most of the requirement will be of the same kind. How will the optimistic container be useful? Regards, V.Janardhanan View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3859245#3859245 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3859245 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
