Bug 1272510

Summary: The "/execute" operation for REST remote API has seen some changes which should be included in the Migration Guide
Product: [Retired] JBoss BPMS Platform 6 Reporter: Musharraf Hussain <mhussain>
Component: DocumentationAssignee: brms-docs <brms-docs>
Status: CLOSED EOL QA Contact: Lukáš Petrovický <lpetrovi>
Severity: high Docs Contact:
Priority: high    
Version: 6.1.0CC: brms-docs
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
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: 2020-03-27 19:08:16 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 Musharraf Hussain 2015-10-16 15:26:13 UTC
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