Ticket #491 (closed Enhancement: fixed)
Namespaces for property keys
| Reported by: | jri | Owned by: | jri |
|---|---|---|---|
| Priority: | Major | Milestone: | Release 4.2 |
| Component: | DeepaMehta Standard Distribution | Version: | 4.1 |
| Keywords: | Cc: | dgf, Malte | |
| Complexity: | 3 | Area: | Application Framework / API |
| Module: | deepamehta-core |
Description
Now where the property storage facility is open to plugins (#472) the property keys must be namespaced. That is instead a sole "property name" a "property URI" must be used.
Change History
comment:2 Changed 11 years ago by jri
Core: namespace property keys (#491).
The Core Service's property API uses property URIs instead of property names.
DEVELOPER NOTE
If your plugin stores its own properties do namespace the property keys.
Use the plugin URI as a prefix for your property URIs.
See #491.
Changeset: ba12bd326af7e1f9e30ce4e9579f8ad731fe2cf1
comment:3 Changed 11 years ago by jri
Time plugin: adapt to property URIs (#491).
Time properties are namespaced:
- "created" -> "dm4.time.created"
- "modified" -> "dm4.time.modified"
See #491.
Changeset: c8d4153a74dbda154b135d2599737461981d9a84
comment:4 Changed 11 years ago by jri
Access Control: namespace properties (#491, #458).
DB property keys are namespaced:
- "creator" -> "dm4.accesscontrol.creator"
- "owner" -> "dm4.accesscontrol.owner"
- "acl" -> "dm4.accesscontrol.acl"
A migration that transforms the DM 4.1 property keys is included.
Note: while migrating the "creator" and "owner" values are indexed. So the new user-based retrieval methods can be used also when updating from DM 4.1 (#458).
Changeset: 5a4fde7fa5d53102e599b82d5de3b7d0aaa12809
