User Story #1233 (closed)
Opened 14 years ago
Closed 13 years ago
Server needs to return an error number for message lookup
Reported by: | atarkowska | Owned by: | jamoore |
---|---|---|---|
Priority: | critical | Milestone: | OMERO-Beta4.2 |
Component: | General | Keywords: | n.a. |
Cc: | cblackburn | Story Points: | n.a. |
Sprint: | n.a. | Importance: | n.a. |
Total Remaining Time: | n.a. | Estimated Remaining Time: | n.a. |
Description (last modified by jmoore)
This may also be the beginning of a general exception rework, so:
- New exceptions
- ObjectNotFoundException (RowNotFound?)
Change History (5)
comment:1 Changed 14 years ago by jmoore
- Cc cblackburn added
- Milestone changed from OMERO-Beta4 to OMERO-Beta4.1
- Priority changed from major to critical
- Summary changed from Server needs to return an error number what can be used a number for lookup to Server needs to return an error number for message lookup
- Type changed from defect to User Story
comment:2 Changed 14 years ago by jmoore
- Description modified (diff)
comment:3 Changed 14 years ago by jmoore
- Milestone changed from OMERO-Beta4.1 to OMERO-Beta4.2
Won't be done for Paris, pushing again.
comment:4 Changed 13 years ago by jmoore
- Milestone changed from OMERO-Beta4.2 to Unscheduled
comment:5 Changed 13 years ago by jmoore
- Milestone changed from Unscheduled to OMERO-Beta4.2
- Resolution set to duplicate
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Unfortunately a bit too broad for 4.0. Pushing.