DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=43136>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=43136 ------- Additional Comments From [EMAIL PROTECTED] 2007-08-22 02:11 ------- Now the optimistic usecases lock their objects right before the execution. Actually this is not a correct behaviour from the user's point of view - if she relied on the state of a resource when the confirmation screen is shown, the resource might now change while she fills in the form. I see this rather as a workaround until we can lock single sitetree nodes. The error ("object has been modified") can still occur if another session is committed while the usecase is executed, but the probability is reduced. To avoid even this, we could synchronize AbstractUsecase.execute() globally, but I wouldn't recommend this. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
