Bug 990490 - Error msg returned when trying to get specific process variable log via REST
Summary: Error msg returned when trying to get specific process variable log via REST
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
high
Target Milestone: ER2
: 6.0.0
Assignee: Marco Rietveld
QA Contact: Radovan Synek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-31 09:50 UTC by Radovan Synek
Modified: 2016-09-20 05:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:13:09 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Radovan Synek 2013-07-31 09:50:47 UTC
After I launched a process I wanted to get a history of changes of a variable 'count':
http://localhost:8080/business-central/rest/runtime/org.jboss.qa.bpms:clustering:1.0.0.Final/history/instance/4/variable/count

However, instead of requested data I got error msg:
<response>
    <status>BAD_REQUEST</status>
    <url>/business-central/rest/runtime/org.jboss.qa.bpms:clustering:1.0.0.Final/history/instance/4/variable/count</url>
    <error>No runtime manager could be found for domain 'count'.</error>
</response>

I should mention that there are rows in the VariableInstanceLog table for this variable.

Very probably the problem is that org.kie.services.remote.rest.RuntimeResource uses the same @PathParam("id") for both deployment and variableId - take a look at the error msg: No runtime manager could be found for domain 'count'. 'count' is the name of the variable

tested with 6.0.0.CR1

Comment 1 Marco Rietveld 2013-08-09 11:09:10 UTC
Fixed, with this commit: 

https://github.com/droolsjbpm/droolsjbpm-integration/commit/5059e60c96d2d15af9dd30661e1120bf86c69c08

(Is ER1 the right target milestone? Or ER2?)

Comment 2 Radovan Synek 2013-09-04 12:08:12 UTC
Verified on BPMS 6.0.0.ER2


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