REST API Bug
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2013 08:09 AM
Hi,
I have noticed a very little bug in rest api.
With the current api, if you want to unclaim a task, you have to claim a task with assignee = null but Rest-api throws an exception when assignee is null.
Just remove the throwing in TaskResource to solve the problem.
Jean-Pascal
I have noticed a very little bug in rest api.
With the current api, if you want to unclaim a task, you have to claim a task with assignee = null but Rest-api throws an exception when assignee is null.
Just remove the throwing in TaskResource to solve the problem.
Jean-Pascal
Labels:
- Labels:
-
Archive
4 REPLIES 4
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2013 04:10 AM
Jean-Pascal,
Thanks for reporting this. Seems like a valid fix for the problem, allowing the assignee in the payload to be null, when claiming. Will fix this in 5.15…
Thanks for reporting this. Seems like a valid fix for the problem, allowing the assignee in the payload to be null, when claiming. Will fix this in 5.15…
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2013 04:27 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-17-2013 02:48 AM
I have created code for process attachment and I have found a little bug in RestResponseFactory in createAttachementResponse.
In your code :
if(attachment.getProcessInstanceId() != null) {
result.setTaskUrlsecuredResource.createFullResourceUrl(RestUrls.URL_PROCESS_INSTANCE, attachment.getProcessInstanceId()));
}
This should be :
if(attachment.getProcessInstanceId() != null) {
result.setProcessInstanceUrl(securedResource.createFullResourceUrl(RestUrls.URL_PROCESS_INSTANCE, attachment.getProcessInstanceId()));
}
In your code :
if(attachment.getProcessInstanceId() != null) {
result.setTaskUrlsecuredResource.createFullResourceUrl(RestUrls.URL_PROCESS_INSTANCE, attachment.getProcessInstanceId()));
}
This should be :
if(attachment.getProcessInstanceId() != null) {
result.setProcessInstanceUrl(securedResource.createFullResourceUrl(RestUrls.URL_PROCESS_INSTANCE, attachment.getProcessInstanceId()));
}
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-17-2013 03:39 AM
Thanks for reporting, I'll fix this on master now so it get's in the 5.15 release…