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.
Original submitter: sunflower Description Netbeans 5.5 Preview (build 2006.02.08) Steps to reproduce: - Add 'TestClass' class element under Model node in UML project tree - Invoke 'Generate Dependency Diagram' on 'TestClass' element node *** 'TestClassDependencies' class diagram is created - Go to the 'TestClassDependencies' class diagram - Put class element from palette on the diagram and name it 'MyClass' *** 'MyClass' class element is added *** 'Nested' link is not created from 'MyClass' to 'TestClass'. - Select 'MyClass' class element on the diagram and invoke 'Navigate to Source' Result: The 'MyClass' class is an inner class of 'TestClass' class so 'Nested' link should be shown between 'TestClass' and 'MyClass' class elements on the diagram.
We do not automtically create link on the diagram. If the user wants the link, they should use the relationship discover button. We are not going to try to read the user mind.
It is not true. Try to put two classes on the class diagram, go to source code ofthe second class and extends it from the first class. The 'Generalization' link appears on the class diagram without any addition user's actions. Please, add the 'nested' link in the same way.
Source to model is a different issue. We are not talking about source to model in this issue. In this issue you are taking control of the drawing by drawing the diagram. By putting the model element into a diagram that is owned by a namespace means that the element is owned by the namespace. When you draw a model element that is owned by a package, we do not automactically draw the nested relationship to the outer package (if it is present on the diagram). It is reduntent and clutters up the diagram (because just about every element in the diagram will have the nested relationship.) In the source to model situation, we are drawing the diagram based on the source code. Basically you are talking about the difference between wearing a coders hat and wearing a modelers hat. When you drag a model element from the project tree onto the diagram, we will create the relationships for you. That is because we found that is what user want. Also most UML tools do the same. But none of the tools discover relationships when you drop a new model element onto a diagram. If we put nested links all over the place the diagram would be cluttered.