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 96305 - can't create second sequence diagram in interaction
Summary: can't create second sequence diagram in interaction
Status: RESOLVED INVALID
Alias: None
Product: uml
Classification: Unclassified
Component: General (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@uml
URL:
Keywords: REGRESSION
Depends on:
Blocks:
 
Reported: 2007-02-22 14:22 UTC by Andrew Korostelev
Modified: 2007-02-22 15:51 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 Andrew Korostelev 2007-02-22 14:22:45 UTC
If user has created sequence diagram, the only way to create new diagram from
it's element's is CDFS.
But user can't create second sequence diagram in the same interaction.

It was allowed in Coco.

steps:
- create uml project
- create sequence diagram.
interaction with sequence diagram will be created.
- invoke 'Create Diagram From Selected Elements' on Interaction node.
It is prohibited to create second sequence diagram in the same interaction
Comment 1 Andrew Korostelev 2007-02-22 14:35:43 UTC
Error message is displayed on attempt to create second SQD.
Creation of another interaction diagram type (collaboration) is also prohibited, 
but without any message - lack of message is filed as separate issue 96307
Comment 2 Trey Spiva 2007-02-22 15:51:56 UTC
his one may have been allowed in Coco, but it should not have been.  I think that in buzz, or bow this 
was not allowed.  It does not make sense to allow two sequence diagrams under a single interaction.  It 
does make sense to allow a collaboration and a sequence diagram under the same interaction, because 
they are different views of the same data.

UML was designed so the interaction contains the information in a sequence diagram (or collaboration).  
It was not designed for one interfaction to support two different sequence diagrams.  It is actually kind 
of fishy that we allow collaboration and sequence diagrams in a single interfaction.  This should be 
allowed because, it is convient for the user because some like the collaboration diagram and some like 
the sequence diagram.  So, I can see that in the same company people could go back and forth between 
the diagrams.