Task #1706 (new)
Server should raise specific exception on conflicting deletes
|Reported by:||jamoore||Owned by:||jamoore|
Unless we serialize all deletes (or other specific actions), delete issues like in #1654 are most likely best handled by using an OptimisticLockException (or a subclass thereof) to inform clients that two deletes happened at the same time.
Does there need to be more information in the exception so that a client can properly display to the user "oh, you just tried to delete that!" ?