Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1222843 - JSON request are not supported in /containers/{id}
JSON request are not supported in /containers/{id}
Status: VERIFIED
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Kie-Server (Show other bugs)
6.1.0
Unspecified Unspecified
high Severity high
: ER3
: 6.2.0
Assigned To: Edson Tirelli
Karel Suta
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-05-19 05:43 EDT by Anton Giertli
Modified: 2015-10-06 04:45 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Anton Giertli 2015-05-19 05:43:14 EDT
Description of problem:
it is not possible to send JSON POST REST Request to  /containers/{id} endpoint of Decision Server.

JSON is supported only for provisioning api- E.g: create-container, list-containers, dispose-container and call-container.

but not for actual rule execution - i.e. fire all rules

Version-Release number of selected component (if applicable):
6.1.0

How reproducible:
always

Steps to Reproduce:
1. Send JSON command to the decision server, i.e.:
{"batch-execution":{"commands":[{"insert":{"out-identifier":"f1","return-object":true,"entry-point":"DEFAULT","object":{"com.esrx.ref.testproject.Bean1":{"name":"Robert"}}}},{"fire-all-rules":{"out-identifier":"myFireCommand"}}]}}

2. Server responds with:
<response type="FAILURE" msg="Error calling container SecondContainer: com.thoughtworks.xstream.io.StreamException:  : only whitespace content allowed before start tag and not { (position: START_DOCUMENT seen {... @1:1) "/>

Actual results:
JSON commands are not supported

Expected results:
JSON commands are supported

Additional info:
Comment 6 Edson Tirelli 2015-09-04 15:10:16 EDT
This is done in 6.2
Comment 7 Karel Suta 2015-10-06 04:45:35 EDT
Verified in 6.2.0.ER3.

Note You need to log in before you can comment on or make changes to this bug.