User Story #113 (new)
Opened 18 years ago
Last modified 18 years ago
Define and use meta-attributes on types in DSL.
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | minor | Milestone: | Unscheduled |
| Component: | DSL | Keywords: | n.a. |
| Cc: | sfrank | Story Points: | n.a. |
| Sprint: | n.a. | Importance: | n.a. |
| Total Remaining Time: | n.a. | Estimated Remaining Time: | n.a. |
Description
Types need access-control attributes. This should prevent the creation of system-level objects (Experimenter, Event, etc.)
See Access Control tiki page for a brief discussion.
This requires changes not just to the DSL but also to the security infrastructure, specifically the Hibernate listeners, the UpdateImpl?, the UpdateFilter? and possibly other classes.
Types and properties also need mutability constraints. This should be easier to implement.
These attributes should get stored in the db (possibly via types.vm) and be accessible from ITypes (#86).
While we're at it, add namespace support with locked and restricted namespaces (core, meta, sys, etc.) This applies even if we use something like EMF:
EmfAsDsl tiki page.
Originally http://bugs.openmicroscopy.org.uk/show_bug.cgi?id=657
Change History (3)
comment:1 Changed 18 years ago by jmoore
- Keywords iteration3 added
- Milestone set to cycle1
comment:2 Changed 18 years ago by jmoore
- Keywords iteration3 removed
- Milestone changed from cycle1 to cycle2
As mentioned in a comment to #86 regarding r704 and r705, this is not fully needed for the current needs (i.e. adding annotations as another user #52). Moving to cycle2. There we'll be full in security-swing #114, and the switch to annotations #96 should have begun so that it makes sense to touch code-generation.
comment:3 Changed 18 years ago by jmoore
- Milestone changed from 3.0-M3 to Future
This is no longer needed for access control. It does play a role, though, but if we switch to EMF becomes unimportant. Moving to Future.
This is required for #86.