[DOCU-1042] Provide a concept for "Create a custom Java-based REST endpoint" doc page Created: 12/Jun/17 Updated: 03/Jul/17 Resolved: 19/Jun/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Christoph Meier | Assignee: | Christoph Meier |
| Resolution: | Done | Votes: | 0 |
| Labels: | core | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoR: |
Empty
|
||||
| Sprint: | Docu Sprint 26 | ||||
| Story Points: | 2 | ||||
| Description |
|
The task of creating a custom Java-based REST endpoint is advanced. When providing the "full CRUD" cycle (create, update, delete) - offering GET, POST, PUT and DELETE methods, one must write a bunch of Java classes. (Actually, it already needs a lot of stuff just for GET). The concept for such a doc page should provide first The output of the doc must be clearly helpful for its audience. |
| Comments |
| Comment by Christoph Meier [ 19/Jun/17 ] |
|
Partially resolved. All clear besides "how far to go" concerning an endpoint which supports all methods ( GET, PUT, POST and DELETE). |
| Comment by Christoph Meier [ 19/Jun/17 ] |
|
Since the next step - the "how to doc" - starts on the next sprint, i close this one - even it is not fully resolved. |