Bug 1310208 - When converting .xls to GDT, globals defined with short class names are converted to invalid Globals file
Summary: When converting .xls to GDT, globals defined with short class names are conve...
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.2.0
Hardware: x86_64
OS: Unspecified
unspecified
high
Target Milestone: ER1
: 6.3.0
Assignee: manstis
QA Contact: Tomas David
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-19 18:21 UTC by David Murphy
Modified: 2020-03-27 19:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 19:12:17 UTC
Type: Bug


Attachments (Terms of Use)
Decision table with global variable (11.50 KB, application/x-ole-storage)
2016-02-19 18:21 UTC, David Murphy
no flags Details

Description David Murphy 2016-02-19 18:21:37 UTC
Created attachment 1128622 [details]
Decision table with global variable

Description of problem:
When converting .xls to GDT, globals defined with short class names are converted to invalid Globals file.

Using the .xls directly, the generated drl contains both the import and the global definition, and thus compiles fine. However, after conversion, the GDT contains the import, and the Globals file contains the global definition with the short class name. This fails validation.


How reproducible:
Always


Steps to Reproduce:
1. Create a .xls decision table which imports java.util.List (see attached)
2. Add a global with type List
3. Import .xls into business-central
4. Convert to Guided Decision Table
5. Open generated Globals Definition
6. Click "validate"

Actual results:
Validation Error:	
Unable to find class 'List'


Expected results:
Globals file passes validation


Additional info:
The project will build/deploy successfully, however attempting to use it will result in 
GlobalError: list : Unable to find class 'List' 
at runtime

Comment 6 Tomas David 2016-03-24 08:31:37 UTC
Verified with BRMS 6.3.0.ER1.


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