Bug 975400 - Process instance identifier is missing in response of start REST API call
Summary: Process instance identifier is missing in response of start REST API call
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: DR6
: 6.0.0
Assignee: Marco Rietveld
QA Contact: Ivo Bek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-18 11:30 UTC by Ivo Bek
Modified: 2016-09-20 05:04 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:06:12 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ivo Bek 2013-06-18 11:30:18 UTC
Description of problem:

When I call start REST API operation to create a process instance, I will receive just this response:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<response>
    <status>SUCCESS</status>
    <url>/business-central/rest/runtime/org.jboss:integration:1.0.0.Final/process/integration.src.main.resources.remotekbase.ScriptTask/start</url>
</response>

There should be some information about the process instance identifier to get more details about the process instance, I created.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Ivo Bek 2013-06-19 11:14:43 UTC
Well, to support it ... the response should be same as JMS, which returns JaxbProcessInstanceResponse.

Comment 2 Marco Rietveld 2013-06-28 15:24:23 UTC
Hi Ivo, I disagree with comparing the JMS and the REST api with each other -- they are not interchangeable and have different purposes, I think. 

The JMS api only really provides a "execute" interface, to which commands can be sent. It also has much less interactivity (and is smaller) than the REST api. If you interface with the JMS api, then the results are determined by which (drools/jbpm) command you call, or if you're using the programmatic client api, which (ksession) method you call. 


I agree with you that more details should be provided, though. I disagree with returning the ProcessInstance: there are other operations for that, including the /process/instance/{id}. 

I'll make sure to add more info to the reply.

Comment 3 Marek Baluch 2013-07-04 18:22:59 UTC
Hi Marco,

which commands? Is it any command which implements the GenericCommand<T> interface?

Thanks!
@M

Comment 4 Marco Rietveld 2013-07-08 18:09:35 UTC
Ivo: I've modified the process/instance/{id}/start method so that it will respond with a JaxbProcessInstance entity.

Comment 5 Ivo Bek 2013-07-09 06:42:35 UTC
I've seen the changes in source code already, so thank you.

Comment 9 Ivo Bek 2013-07-11 08:38:16 UTC
Verified in JBoss BPMS 6.0.0.DR6


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