Bug 1297045

Summary: BPM Design Does Not Show Imports For Data Objects Which In a Dependent Jar
Product: [Retired] JBoss BPMS Platform 6 Reporter: Justin Holmes <jholmes>
Component: Business CentralAssignee: Tihomir Surdilovic <tsurdilo>
Status: CLOSED EOL QA Contact: Lukáš Petrovický <lpetrovi>
Severity: unspecified Docs Contact:
Priority: high    
Version: 6.2.0CC: kverlaen
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:13:45 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
1
none
2
none
3 none

Description Justin Holmes 2016-01-08 20:46:39 UTC 
Created attachment 1112986 [details]
1

Description of problem:
When creating a process definition a kmodule that depends on another jar to provide the fact model, the designer does not show the objects in it's drop down lists.

Version-Release number of selected component (if applicable):
6.2.0 GA and 6.1.4 GA

How reproducible:
100%

Steps to Reproduce:
1. Create a kmodule
2. Add a different jar as a dependency which has a fact model
3. Update package white list to allow new classes in editors. http://www.schabell.org/2015/12/jboss-bpmsuite-data-models-whitelist-imports.html
4. Attempt to create a process variable declaration in process designer

Actual results:
Drop downs for import and class type do not have the new classes from the fact model. see 1.png

Expected results:
Drop down is populated with new classes (a la 2.png)

Additional info:
DRL editor show the dependencies just fine (see 3.png). If you import the fact model jar as a project into business central, the design seems to load the classes correctly (2.png)
Comment 1 Justin Holmes 2016-01-08 20:47:06 UTC 
Created attachment 1112987 [details]
2
Comment 2 Justin Holmes 2016-01-08 20:47:29 UTC 
Created attachment 1112988 [details]
3
Comment 4 Kris Verlaenen 2016-01-10 21:59:51 UTC 
These are limitations from the query service that designer is using underneath currently.  DRL editor is using a different service, which seems to be much better when it comes to searching for classes in a project however.