-
Type: Task
-
Status: Open
-
Priority: Minor
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: QualifiedToSchedule
-
Component/s: Automation, WebEngine
Automation is more a RPC system than a Rest binding.
It does actually use JAXRS, but the Rest resource is the Operation it-self :
- calling GET will give you the definition
- calling POST will execute it
Having a simple RESTful CRUD API would help :
- simple testing
- integration with Javascript MVC model
The goal if this task is to build a CRUD RESTful API on Document and adapter.
Here we are talking about reverting the Automation paradigm :
- the Resource if the document and not the Operation
- the Operation is the Http Verb and is limited to CRUD
We could build that as an extension of the existing Automation.
This basically means that Automation exposes 3 endpoints :
- Operation RPC endpoint (/site/automation/${operationId})
- Operation RPC batch endpoint (/site/automation/batch)
- RESTFull/CRUD
This new CRUD API should focus on CRUD on a DocumentModel or it's adapter.
On the contrary to Operations, CRUD API can not be combined inside an AutomationChain and don't need to appear inside Studio.
Target url pattern could be :
- for pure CRUD : GET / PUT / POST / DELETE on
/site/automation/nxdoc/{repo}/{uuid}©{adapter}
- for execute an operation on the target doc : GET or POST on
/site/automation/nxdoc/{repo}/{uuid}/{operation}@{adapter}
1.
|
CRUD REST Binding for DocumentModel | Resolved | Damien Metzler | ||||||||
2.
|
Domain model object and Automation | Resolved | Damien Metzler | ||||||||
3.
|
Provide a sample app (JS + HTML) based on CRUD API | Resolved | Damien Metzler | ||||||||
4.
|
Add a support for simple management of Attachements | Open | Unassigned |
|
|||||||
5.
|
Make REST Binding URL Scheme resolved pluggable | Open | Unassigned |
|