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 80589 - attribute type property is 'void' after attribute creation from source
Summary: attribute type property is 'void' after attribute creation from source
Status: RESOLVED WONTFIX
Alias: None
Product: uml
Classification: Unclassified
Component: Synchronization (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: issues@uml
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-19 13:30 UTC by bugbridge
Modified: 2007-01-19 07:07 UTC (History)
1 user (show)

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 bugbridge 2006-07-19 13:30:32 UTC
Original submitter: sergeyp

Description:

steps to reproduce:
1. create package with scoped class diagram
2. add class to the diagram
3. navgate to source (from class element)
4. enter 'private float f;'
5. wait
6. go to model
7. select the attribute in class element on the diagram
type property is 'void'
8. add 'private float u' attribute with edit control
9. select last attribuute
type property is 'void'
Comment 1 Craig Conover 2006-08-11 00:38:25 UTC
Review: bug is as stated. The type is correct on the element in the diagram and
in the UML project tree, but not in the property sheet.
 
Comment 2 Craig Conover 2006-08-11 00:44:25 UTC
Observation: I assume that the list of Types for this property comes from the
DataType, Class and Interface elements (possibly other element types) in the UML
project. float is one of the DataType elements, but it doesn't appear in the
dropdown list for this property, but the others in the project do.
Comment 3 Craig Conover 2006-08-11 01:35:44 UTC
Upon further investigation, I notice that if an attribute is added to the source
code with a primitive datatype that is not yet represented in the UML project,
then it doesn't get added to the Type property's pick list in the PropertySheet.

If it is added to the UML element on the diagram, it is added properly. Or, if
it is not a primitive (a real Object type), and it added to the source file,
then it is added to the pick list for the Type property.

Look into PickListManager and TypeManager classes (in core UML) for a starting
point. The PickListManager is not being populated properly when new type added
via source code.
Comment 4 Peter Lam 2007-01-19 07:07:35 UTC
live round-trip feature.