Bug 1272510 - The "/execute" operation for REST remote API has seen some changes which should be included in the Migration Guide
The "/execute" operation for REST remote API has seen some changes which shou...
Status: NEW
Product: JBoss BPMS Platform 6
Classification: JBoss
Component: Documentation (Show other bugs)
6.1.0
All All
high Severity high
: ---
: ---
Assigned To: brms-docs@redhat.com
Lukáš Petrovický
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-10-16 11:26 EDT by Musharraf Hussain
Modified: 2016-01-08 16:58 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Build Name: 23049, Migration Guide-6.1 Build Date: 31-07-2015 11:17:09 Topic ID: 43045-757057 [Latest]
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 Musharraf Hussain 2015-10-16 11:26:13 EDT
Title: Migrating Client Application APIs from 6.0.x to 6.1

Describe the issue:
- The "/execute" operation for REST remote API has seen some changes which should be included in the Migration Guide. Some of the changes are mentioned in this KCS [1] for your reference. Here I quote it's contents for your quick reference. Please review them and try to incorporate them in the mainstream documents like Migration Guide.
~~~
If you are using BPM Suite 6.1 notice that the API has changed. Users of the remote API should not be affect by these details. Here is the list of changes:

    The endpoint changed to /execute;
    For the client we now must use the org.kie.remote.jaxb.gen package classes which are in the org.kie.remote:kie-remote-client artifact;
    The client artifacts will only accept commands from this package, for other packages we will have errors and will not allowed to send commands;
    The deployment ID is set using a new HTTP header Kie-Deployment-Id that is also available using the Java constant JaxbSerializationProvider.EXECUTE_DEPLOYMENT_ID_HEADER.

~~~

[1] https://access.redhat.com/solutions/909913

Suggestions for improvement:
- Please update the Migration Guide with the changes suggested above.

Additional information:
- Nothing

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