snoopdave opened a new pull request, #209:
URL: https://github.com/apache/roller/pull/209

   Stacked on #161 (base: `replace-propono-atompub`). Review only the commit on 
top of it.
   
   Adds three collections to each weblog's AtomPub workspace. The service 
document lists a collection only when the user may use it.
   
   | Collection | Who | Methods |
   |---|---|---|
   | `/{handle}/templates`, `/template/{id}` | Weblog admins, custom theme 
only, site allows custom themes | GET, POST, PUT, DELETE |
   | `/{handle}/categories`, `/category/{id}` | Users with POST permission | 
GET, POST, PUT, DELETE (`?moveTo={id}` for a category in use) |
   | `/{handle}/categories.atomcat` | Users with POST permission | GET (RFC 
5023 category document) |
   | `/{handle}/comments`, `/comment/{id}` | Users with POST permission | GET 
(`?status=`, `?entry=`), PUT (status only), DELETE |
   
   - **Templates:** `atom:content` is the standard rendition and 
`roller:rendition type="mobile"` the mobile one. An empty mobile rendition 
removes it (new `WeblogManager.removeTemplateRendition()`). The template rules 
move from the Templates/TemplateEdit pages into `WeblogTemplateEditor`, so the 
UI and AtomPub share them.
   - **Categories:** the entries collection keeps its inline category list and 
also references the new category document.
   - **Comments:** moderation only, with the same approval email and reindexing 
as the Comments page. `thr:in-reply-to` (RFC 4685) links to the entry.
   - Extension namespace: `http://roller.apache.org/ns/atompub/1.0`. The user 
guide documents the URIs and elements.
   
   Tests: integration tests on Derby for all three collections (permissions, 
custom-theme rule, cross-weblog ids, conflicts), `WeblogTemplateEditorTest`, 
schema validation of the new formats against the RFC grammars, and handler 
routing. `mvn -pl app test`: 524 tests, 0 failures. Not yet tested over the 
wire against a running server.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to