Consistency question on REST API (process instance)
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2012 10:35 AM
Hi everybody,
while integrating the REST API into my own app and playing around with it, I found a consistency issue in the area of the processs instance.
According to the documentation ( http://activiti.org/userguide/index.html#N1293E ) and my experiments, one creates a process instance by issuing a POST to
However, any other action with the process instance is done by using processInstance as entry point, e.g. in order to get the details of an instance one needs to issue an GET to
Is there a specific reason for the different entry points?
Regards
Oliver
while integrating the REST API into my own app and playing around with it, I found a consistency issue in the area of the processs instance.
According to the documentation ( http://activiti.org/userguide/index.html#N1293E ) and my experiments, one creates a process instance by issuing a POST to
/process-instance
However, any other action with the process instance is done by using processInstance as entry point, e.g. in order to get the details of an instance one needs to issue an GET to
/processInstance/{processInstanceId}
Is there a specific reason for the different entry points?
Regards
Oliver
Labels:
- Labels:
-
Archive
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2012 02:57 AM
Oliver,
There is no specific reason for that, probably an oversight with has been there from the beginning… To ensure backwards-compatibility, this will be kept I guess. However, feel free to add a Jira which describes this, it's always possible to add additional URL-mapping for the rest-resource to be consistent.
There is no specific reason for that, probably an oversight with has been there from the beginning… To ensure backwards-compatibility, this will be kept I guess. However, feel free to add a Jira which describes this, it's always possible to add additional URL-mapping for the rest-resource to be consistent.
