I do think the performing retries automatically, i.e. as part of the API, can lead to some strange effects. The reason that the optimistic locking fails is normally that someone else has modified the node in the meantime. Since the node contains data that is relevant to the application, the application is the only place where I can decide if I would like to keep these changes or if I want to replace them with the data of my original transaction. This said I think the only valid solution (even in the case with no transactions) is to throw an exception (maybe a special type) and let the application do the rest.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3905078#3905078 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3905078 ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
