Metadata
- Source
- ENGAGE-345
- Type
- Task
- Priority
- Blocker
- Status
- Closed
- Resolution
- Fixed
- Assignee
- Colin Clark
- Reporter
- Colin Clark
- Created
2010-02-08T16:30:05.000-0500 - Updated
2014-03-03T14:12:35.838-0500 - Versions
-
- 0.3b
- Fixed Versions
-
- 0.3b
- Component
-
- My Collection
Description
Previously My Collection's "collectionOperations" service implemented resource oriented URLs by actually changing EngageApp.js. These changes caused other services to break.
In order to implement URLs like this:
/users/[userId]/artifacts/[artifactId]
- POST collects the specified artifact
- DELETE uncollections
We should create a custom acceptor that will parse the pathInfo and do the right thing.
Attachments
Comments
-
Colin Clark commented
2010-02-08T16:30:19.000-0500 Bug Parade Engage 0.3
-
Colin Clark commented
2010-02-08T20:40:09.000-0500 Here's an in-progress patch that includes a new acceptor for the collectionOperations service. I've managed to break Artifact View, so this isn't quite functioning yet, but we're close.
-
Svetoslav Nedkov commented
2010-02-09T08:31:23.000-0500 A new patch added on top of the "a" patch.
Changes to the rendering options for artifact view so that the collect link and status are shown.
Changed resource oriented URL parsing.
Changed My Collection service to properly parse the query parameters. -
Colin Clark commented
2010-02-16T11:57:22.000-0500 This issue was addressed in the myCollection-tryout branch last week. It still needs to be committed to trunk and then reviewed.