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.
It is not allowed to create second collaboration or sequence diagram in the same interaction. e.g. CDFS doesn't allow this. Bit it is possible with 'Save As' action. steps: - create uml project - create collaboration diagram. - invoke 'Create diagram on Selected Eloements' on interaction node. It is not allowed to create the second collab. diagram in the same interaction. - invoke 'save as' on collaboration diagram node. - type new name and press 'OK' New collab diagram will be created in the same interaction.
I guess it's not allowed to create two sequence or collaboration diagrams for the same interaction mainly because the elements and their relationship that form the sequence or collaboration diagrams are already determined given the same interaction object. But we overlooked the need that user might want to have another diagram with same information but different presentation / layout. This restriction sounds too strong and unnecessary to me, I'll leave it for iteam to decide.
There is a question if it should be the same interaction to represent interaction in another layout or may be it's better to create copy of interaction on save action? In my opinion diagram is a representation of an interaction and user may want to add some new elements to one of copies and do not ad to another, is it ok? if ok we may want to cancel limitation for cdfs and 'New|DiGRAM' action also
Save As should be disabled under the interaction node. As for New->Diagram on the interaction node, the Create New Diagram checks for multiple sequence diagrams under the same interaction node so the Finish button is not enabled if multiple sequence diagram is to be created.
removed 'Save As' on interaction diagram nodes (collaboration and sequence), per team's decision.
an enhancement requst to copy the whole interaction to a new interaction is now being tracked by issue 110073.
verified in build 070719
I think sergeyp had a good point - I could imagine interactions that could be captured by more than one diagram, in order to present "summary" vs. "detail" views of what is going on. It would be just one interaction, and I would be happy with just one model, but where each diagram could choose to hide or show individual elements in the interaction. Along similar lines - I am not sure whether you meant a "use case", when you mention an "interaction". If so, it would still make sense to allow more than one diagram, and it would also make sense to allow for different elements to appear in different diagrams. It seems to me the diagrams would correspond to different scenarios within the same use case - and these could have differences...
Since currently we designed the tool around a one interaction one diagram concept, I am making this an enhancement.