Bug 1126776

Summary: Gateway expressions does not respect Import section
Product: [Retired] JBoss BPMS Platform 6 Reporter: Anton Giertli <agiertli>
Component: jBPM CoreAssignee: Kris Verlaenen <kverlaen>
Status: CLOSED EOL QA Contact: Radovan Synek <rsynek>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0.2CC: mbaluch
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 19:35:28 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 Anton Giertli 2014-08-05 09:01:38 UTC
Description of problem:

Even if the model class is properly imported in the Import section, this class can't be resolved in the gateway expression

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

How reproducible:
always

Steps to Reproduce:
1. Create model class using Data Modeler
org.redhat.gss.Person
attribute name:String

2. Create new process, with following structure:

start->xorgateway---expression--> script -> end
                 ---expression--> script -> end 
3. COnfigure the important statements, on the process level, like this:
org.redhat.gss.Person|default
4. Create process variable person:Person
5. Now implement one of the expression, like this:
return  KieFunctions.contains(person.getName(),"admin");
6. Save the process

7. Following can be observed
Person cannot be resolved to a type Person cannot be resolved to a type

Actual results:
Import statements are not respected in the Gateway Expression

Expected results:
Import statements are respected in the Gateway Expression

Additional info:

workaround is to define process variable using FQCN, i.e.

person:org.redhat.gss.Person
instead of
person:Person

Comment 1 Kris Verlaenen 2014-08-18 09:17:08 UTC
Variables should currently always be defined using FQN, this is not just for gateway expressions.