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 78473 - Add Collection Override and Use Generics properties at the Attribute level
Summary: Add Collection Override and Use Generics properties at the Attribute level
Status: RESOLVED INVALID
Alias: None
Product: uml
Classification: Unclassified
Component: Properties (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: Craig Conover
URL:
Keywords:
Depends on: 78539 84855
Blocks: 89954
  Show dependency tree
 
Reported: 2006-06-20 10:04 UTC by bugbridge
Modified: 2007-04-19 20:51 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bugbridge 2006-06-20 10:04:27 UTC
Description:
The Collection Override and Use Generics global properties have little value at
the global level. These options need to be able to be set individually for each
Attribute using the global settins as a default setting.
Comment 1 Craig Conover 2006-09-20 00:46:34 UTC
Much of this work has been done but the roundtrip redesign efforts have put the
completion of this feature on hold so the status is being set to REMIND.
Completion of this issue will have to wait until roundtrip redesign is completed.
Comment 2 Craig Conover 2006-10-11 20:41:03 UTC
This issue should be addressed after Roundtrip Redesign is finished
Comment 3 Craig Conover 2006-10-26 19:24:25 UTC
This enhancement will be implemented as soon as the global preference version of
this enhancement is integrated. The work on the global prefs is finished and
awaiting code review for checkin.
Comment 4 Sergey Petrov 2007-04-10 06:02:35 UTC
To be a complete implementation the same property for methods parameters should
be added, it can be filed as a separate enhancement or be fixed as part of this one.
Comment 5 Trey Spiva 2007-04-10 14:09:25 UTC
There is no need to create a seperate issue.  I was planning to handle parameters with this issue.  On 
multiplicity there will be a new property.  I had to add the property to multiplicity, not attribute and 
parameter.  The reason that the new property was added to multiplicity was to handle multiple 
dimensional multiplicity.

For example, - foo[0..*,0..*] : MyType could be private MyType ArrayList < List < Foo > >; or it could be 
private MyType ArrayList < Foo[] >;
Comment 6 Craig Conover 2007-04-19 20:51:26 UTC
This enhancement was implemented using an alternative design making this obsolete.