Bug 851103 - Existing POJO model w/ nested classes (A$B$C) causing error during build package
Summary: Existing POJO model w/ nested classes (A$B$C) causing error during build package
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: BRM (Guvnor)
Version: BRMS 5.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: manstis
QA Contact: Jiri Locker
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-23 09:09 UTC by manstis
Modified: 2020-04-27 01:14 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Some fully qualified inner class names were being incorrectly parsed and the import statements that were automatically generated for nest classes were incorrect. This caused the completion of knowledge packages with the incorrect import statements to fail, and users had to manually alter the generated import statements. This has been resolved by ensuring the fully qualified inner class names are correctly parsed. The import statements generated for inner classes are now correct, and knowledge packages including import statements for inner classes now compile without the need for manually altering of the import statement.
Clone Of:
Environment:
Last Closed: 2012-09-25 14:49:18 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker GUVNOR-1911 0 Major Resolved Existing POJO model w/ nested classes (A$B$C) causing error during build package. 2012-11-21 06:33:07 UTC

Description manstis 2012-08-23 09:09:45 UTC 
Description of problem:

See linked JIRA.

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

See linked JIRA.

How reproducible:

See linked JIRA.

Steps to Reproduce:
1.
2.
3.
  
Actual results:

Nested classes cause a RTE.

Expected results:

Nested classes can be used in a POJO model.

Additional info:
Comment 2 Jiri Locker 2012-09-25 14:49:18 UTC 
This is not a bug. Existing POJO models with nested classes can be used to build the package. The only step needed is fixing the import section of the package by removing old nested class import statements and adding them again (that will replace '$' separators by dots '.').
Comment 3 manstis 2012-09-25 14:57:56 UTC 
The "fixing" is not automatic, so when importing a model with nested classes the $ is automatically replaced with ".". Likewise when adding an import the $ is replaced with ".". Before the fix for this JIRA you would have to manually view the "Advanced" imports\global view and manually change the $ to ".".
Comment 4 manstis 2012-09-25 14:58:42 UTC 
LOL, typo in comment#3. It should read "The 'fixing' is *NOW* automatic..."
Comment 5 Jiri Locker 2012-09-25 15:14:58 UTC 
OK, then it's verified. Thanks.
Note You need to log in before you can comment on or make changes to this bug.