Bug 1062580 - Java code viewer doesn't show generics properly
Summary: Java code viewer doesn't show generics properly
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Data Modeler
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ER1
: 6.0.1
Assignee: Jan
QA Contact: Zuzana Krejčová
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-07 11:25 UTC by Walter Medvedeo
Modified: 2016-08-01 01:08 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:02:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Walter Medvedeo 2014-02-07 11:25:34 UTC
Description of problem:

When the datamodeller generates a .java file like this:

    
public java.util.List<org.kie.external.ClaseExternalInterface> getInterfaz() {
        return this.interfaz;
    }

public void setInterfaz(java.util.List<org.kie.external.ClaseExternalInterface> interfaz) {
        this.interfaz = interfaz;
    }


If you go to the project browser and click on the .java file, the java code viewer shows somethinig like this:

23.        |            public java.util.List getInterfaz() {
24.        |                return this.interfaz;
25.        |            }
26.        |        
27.        |            public void setInterfaz(java.util.List interfaz) {
28.        |                this.interfaz = interfaz;
29.        |            }


The generics part <org.kie.external.ClaseExternalInterface> is not being shown properly.



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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Jan 2014-02-07 13:26:32 UTC
Fixed in:

Master: http://github.com/droolsjbpm/kie-wb-common/commit/6b91d3984

Comment 2 Jan 2014-02-07 15:35:22 UTC
Fix pushed also into 6.0.x:
http://github.com/droolsjbpm/kie-wb-common/commit/934b5f263


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