You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 5
Next »
Objectives
- Containment Index
- The containment index is designed to be used for:
- Keeping track of which Fedora resources are contained by which Fedora containers (resources)
- Facilitating the generation of 'ldp:contains' triples for responses to Fedora requests
- Success will be defined by:
- Storing containment relationships
- Adding containment relationships when Fedora resources are added to a Fedora container
- Deleting containment relationships when Fedora resources are removed from a Fedora container
- Rebuilding containment relationships on application startup (if the index is empty)
- Providing ldp:contains triples in HTTP responses
- Ensuring the HTML UI renders contained resources
- Ensuring the HTML UI navigates containment relationships
- Initial JMS Messaging infrastructure
- The JMS messaging feature is designed to:
- Implement the Notifications section of the Fedora API Specification
- Per the Fedora messaging documentation
- Success will be defined by:
- Deciding on which message bus to use (was Guava)
- https://github.com/greenrobot/EventBus
- Guava
- ?
- Wiring the bus into the code such that events are put on the bus
- Marshaling messages into the message format
- Publishing of messaging via JMS
- Long running transactions
- ACLs
- Success will be defined by
- All ACL integration tests will be re-enabled
- ACL-aware deletions will function as expected
Tickets
Sprint board
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.