Bug 1092498

Summary: FindVariableInstancesByNameCommand do not work for JMS API
Product: [Retired] JBoss BPMS Platform 6 Reporter: Ivo Bek <ibek>
Component: Business CentralAssignee: Marco Rietveld <mrietvel>
Status: CLOSED CURRENTRELEASE QA Contact: Ivo Bek <ibek>
Severity: high Docs Contact:
Priority: high    
Version: 6.0.2CC: kverlaen, rrajasek, smcgowan
Target Milestone: ER3   
Target Release: 6.0.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-06 19:50:09 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:
Attachments:
Description Flags
Patch for VariableHistoryTest none

Description Ivo Bek 2014-04-29 12:30:06 UTC 
Description of problem:

In BZ 1070097 the history operations were changed so as not to require deploymentId. When I use FindVariableInstancesByNameCommand, I will not get any results though I get the results via REST API.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 3 Marco Rietveld 2014-05-07 01:00:15 UTC 
Created attachment 893048 [details]
Patch for VariableHistoryTest
Comment 4 Ivo Bek 2014-05-07 07:39:45 UTC 
Marco, thank you very much for your effort to fix the problem. I did not notice the onlyFromActiveProcesses property in FindVariableInstancesByNameCommand. 

What do you think about changing the default value of the property to false? I would like to follow Convention over Configuration model and I see this command more appropriate for history process analysis than BAM for active processes.
Comment 5 Marco Rietveld 2014-05-07 09:10:01 UTC 
Hi Ivo, 

I agree with you that the property should be false -- and also that the behavior of the FindVariableInstancesByNameCommand is not at all obvious. 

However, it's part of the API and I'm not sure we can change that in a bugfix release. Kris has the last word on this, I'll check with him.
Comment 6 Ivo Bek 2014-06-08 07:54:21 UTC 
Verified in BPMS 6.0.2.ER3
Comment 7 Kris Verlaenen 2014-06-16 13:24:06 UTC 
Fine with changing the default value if that makes sense (although the ship has sailed for this bug fix release, can be done on master).