Bug 724199 (BRMS-142)

Summary: can't call methods on a global list in test scenario
Product: [JBoss] JBoss Enterprise BRMS Platform 5 Reporter: Jaroslaw Kijanowski <kijanowski>
Component: BRM (Guvnor)Assignee: Toni Rikkola <toni>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: high    
Version: 5.0.0 GA   
Target Milestone: ---   
Target Release: 5.0.2   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/BRMS-142
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-23 11:12:49 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:

Description Jaroslaw Kijanowski 2009-06-22 17:13:16 UTC
Date of First Response: 2010-04-01 03:32:04
securitylevel_name: Public

Comment 1 Jaroslaw Kijanowski 2009-06-22 17:14:48 UTC
Link: Added: This issue depends GUVNOR-377


Comment 2 Jaroslaw Kijanowski 2010-03-23 11:12:49 UTC
Verified in BRMS 5.0.2 CR1
Methods like size can be called on a global (java.util.List) in the EXPECT section

Comment 3 Dana Mison 2010-04-01 07:32:04 UTC
To clarify for the release notes:

"calling a method on a global list in a test scenario"

Would users have encountered an error message or exception being thrown when they tried to do this before ?



Comment 4 Toni Rikkola 2010-04-01 16:22:16 UTC
Before the fix calling size gave the following exception in a popup if the user tried to run the test scenario:

"Unable to run the scenario. could not access/write property (size) in: java.util.ArrayList"

The user was able to add the size to expect section, just running the test scenario failed.

Comment 5 Dana Mison 2010-04-06 01:54:32 UTC
Documented as resolved in the BRMS 5.0.2 release notes:

GUVNOR-377
Test scenarios that contained method calls to List globals (java.util.List) would fail to run, and would display an error dialog. This has been fixed and these method calls now work as expected.