Thanks,
I had looked at your post and you are right the transaction must be
atomized for JBoss optimistic locking to work. My application writers are
adverse to handling their own transactions. I am going to have to
declaratively setup which field in a table is to be checked for concurrency so
I can roll my own optimistic locking for the clients. I will use the JBoss
mechanism for middle tier transactions and use my own for remote invokations.
Jerry
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3859758#3859758
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3859758
-------------------------------------------------------
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
