Skip to content

Restful Content API #386

@wezell

Description

@wezell
  1. Use URL Parameters, with the pattern /key/value/key/value

  2. Take a parameter called /render/true, which if passed in and the resultant content is a widget, we need to parse the widget code and render the widget (Remote Widget)

  3. /api/widget/search <-- renders the widget as XML/JSON

  4. /api/content/search <-- renders the content object as XML/JSON

    NOTE Both of these need to take an ID or Query so /id/uuid or /query/+somequry+ The ID is not a search though. It would be /api/content/find/id/uuid Where search is /api/content/search/query/+somequry+

  5. Allow users to be passed in using username / password (optional, like we do on the AjaxAction)

  6. Add a link from the content search screen (show query dialog) to the restful representation of the content search

NOTES
Leave the JSONContentletServlet mapped. The /api/content is this same servlet.
Would be good to create a base class like we did with AJAXAction for these Servlet APIs and have one mapping like it does in web.xml. So create the new mapping but make sure the JSONContentletServlet still works. If you need to copy the class and leave the old one but deprecate it that is fine.

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions