Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #1706 (new)

Opened 13 years ago

Last modified 13 years ago

Server should raise specific exception on conflicting deletes

Reported by: jamoore Owned by: jamoore
Priority: major Milestone: Unscheduled
Component: API Version: 4.1
Keywords: n.a. Cc: jburel
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.


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!" ?

See #1654

Change History (2)

comment:1 Changed 13 years ago by jmoore

  • Type changed from User Story to Task

comment:2 Changed 13 years ago by jmoore

  • Milestone changed from OMERO-Beta4.2 to Unscheduled

Jean-Marie, I'm moving this to unscheduled. If you think you have time to make use of it, we can add it back in.

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.67230 sec.)

We're Hiring!