Red Hat Bugzilla – Bug 1002927
All REST APIs should use consistent input/output formats
Last modified: 2016-09-20 01:04:57 EDT
Description of problem:
- Business Central REST API uses JSON (only) as input/ouput data format
- Kie (jbpm) remote REST API uses XML (only) as input/output data format.
We should be consistent across the product - so either use only JSON or only XML or ideally both, so users have choice.
Note: Issue is logged under BRM Guvnor component, because the part of it lies there. It could be also filled under some jBPM component, but I can't select more than one component.
Version-Release number of selected component (if applicable):
jbpm will support both xml and json.
All operations, *except the /execute* operation, can now also take or return JSON objects.
The default is JAXB, but if the request contains an "Accept" header that references the "application/json" media type, then the operation will return JSON.
The commit can be found here:
It's not practical to have the /execute operation support JSON because it would impact too many things:
1. All command objects
2. Other projects depending on command object serialization (drools-camel, among others).
Marking this as verified. KIE remote API now supports JSON for almost all operations (see in previous comments) and as Marco explained for rest of them it's not practical to use JSON.