This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 111821 - attribute/operation return types are always "Unnamed"
Summary: attribute/operation return types are always "Unnamed"
Status: VERIFIED FIXED
Alias: None
Product: uml
Classification: Unclassified
Component: Reverse Engineering (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P1 blocker (vote)
Assignee: Yang Su
URL:
Keywords: REGRESSION
Depends on:
Blocks:
 
Reported: 2007-08-02 19:59 UTC by Sherry Zhou
Modified: 2007-08-03 07:19 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sherry Zhou 2007-08-02 19:59:48 UTC
build 070802

Steps:
1. Reverse the following simple method 
 public class Test {
    void setN(){     
    }
    
    public int getN() {
        return 0;
    }
}

2. In uml model, generate one of these operations to   sequence diagram
An Invalid Name dialog shows with the error message below.

The element name specified is not valid. Element names can't be reserved words, cannot contain 
invalid characters and must be valid Java identifiers. The element will revert to the name previously
specified.

In the UML project tree, the operation's type  is changed to Unnamed
Comment 1 Peter Lam 2007-08-02 21:47:01 UTC
This is not just in the re-operation. I think this is the same regression everywhere so I changed the summary instead of
opening a separate issue. I can't add attribute/operation with a valid type. From a class diagram, the following steps
apply to both adding attribute or operation:
- add and name class on the diagram
- right-click on the class and select Insert Attribute
Result: the Invalid Value dialog pops up immediately and changed the initial attribute entry to "private Unnamed Unnamed"
- name the attribue
Result: attribute is named but Invalid Value dialog pops up again
- change the type to a valid type, eg, int, double, etc.
Result: Invalid Value dialog pops up again and type can't be renamed so the type is "Unnamed"
Comment 2 Yang Su 2007-08-03 01:26:35 UTC
the attempted fix for issue 110338 caused this regression, rolled back the change and will investigate a proper fix for
the first issue.
Comment 3 Peter Lam 2007-08-03 07:19:42 UTC
verified in build 070803-b2225