Bug 1002927
Summary: | All REST APIs should use consistent input/output formats | ||
---|---|---|---|
Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Petr Široký <psiroky> |
Component: | Business Central | Assignee: | Marco Rietveld <mrietvel> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Petr Široký <psiroky> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.0.0 | CC: | etirelli, kverlaen, smcgowan |
Target Milestone: | ER5 | ||
Target Release: | 6.0.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-08-06 20:10:42 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Petr Široký
2013-08-30 09:15:49 UTC
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: 6.0.x: https://github.com/droolsjbpm/droolsjbpm-integration/commit/d6815178305320eca2a1ea671ba36d54476bfbc3 master: https://github.com/droolsjbpm/droolsjbpm-integration/commit/d58b76312f57ee4e337f4bbe17dc46dfb4f846d0 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. |