Requirement #252 (closed)
Opened 18 years ago
Closed 9 years ago
Validation umbrella
Reported by: | jamoore | Owned by: | jamoore |
---|---|---|---|
Priority: | minor | Milestone: | Unscheduled |
Component: | ORM | Keywords: | validations, annotations |
Cc: | jburel | Business Value: | n.a. |
Total Story Points: | n.a. | Roif: | n.a. |
Mandatory Story Points: | n.a. |
Description (last modified by jmoore)
Validation has been put on the backburner for quite a while. Hopefully with the move to JPA or at least Hibernate annotations this will get easier. It'll require a new EventListener in EventListenerFactoryBean and lots of hand-written validation. One particular validation is that for a single default group (see #251).
Topics to include:
- Roi shapes should have no nulls although subclassing permits it in the DB.
- ...
Change History (9)
comment:1 Changed 15 years ago by jmoore
- Milestone changed from Unscheduled to Future
comment:2 Changed 15 years ago by jmoore
- Cc jburel added
- Description modified (diff)
- Milestone changed from Unscheduled to OMERO-Beta4.1
comment:3 Changed 15 years ago by jmoore
- Milestone changed from OMERO-Beta4.1 to OMERO-Beta4.2
Pushing.
comment:4 Changed 14 years ago by jmoore
- Milestone changed from OMERO-Beta4.2 to Unscheduled
comment:5 Changed 14 years ago by jmoore
- Type changed from User Story to Requirement
comment:6 Changed 14 years ago by jmoore
- Priority changed from critical to major
Lowering based on 4.2+ priorities.
comment:7 Changed 13 years ago by jmoore
- Priority changed from major to minor
comment:8 Changed 9 years ago by jburel
Josh: Can we close that requirement w/o any story?
comment:9 Changed 9 years ago by jamoore
- Resolution set to invalid
- Status changed from new to closed
After the discussion on user names (#1398) it was decided to not make a special effort on that one front, but to wait and do validation across the board while re-working the model and code generation. Moving this ticket up.