Book a Demo

Author Topic: DB to XML Conversion problem  (Read 2523 times)

ea0804

  • Guest
DB to XML Conversion problem
« on: November 12, 2004, 03:05:45 pm »
We have hundreds of diagrams that have changed during the conversion from our DB storage to XML.   Extra messages (method calls) are displayed on our Sequence diagrams.   We would like to store our documentation in VSS so we went through the process of converting our packages.   Is this a bug or a user error?  

I'm continuing to narrow down a simple case that I can recreate.   Note, the DB to EAP format seems to have worked well.   I'm noticing the extra messages appear  after I add the diagrams to VSS and then perform "Get Latest".    The messages between the two objects are valid on other sequence diagrams.   It seems like "Get Latest" lists all messages between the two objects regardless of the individual diagram.  
« Last Edit: November 15, 2004, 11:26:43 am by ea0804 »

thomaskilian

  • Guest
Re: DB to XML Conversion problem
« Reply #1 on: November 13, 2004, 10:32:54 am »
Leo,
from your post one can't really figure out what exactly you have been doing. Maybe you should elaborate a bit more on "how" and "what".

ea0804

  • Guest
Re: DB to XML Conversion problem
« Reply #2 on: November 16, 2004, 08:07:16 am »
I've been able to recreate a problem of sequence diagram messages disapearing under a simple senario.

1) Create two views: class and sequence.
2) Under class, create two classes (one with two operations).
3) Under sequence, create two sequence diagrams.  Each diagram has both classes but uses a different operation messages.
4) Store the class view in Visual Source Safe.
5) On one of the sequence diagrams, add the other operation message and save the diagram.
6) "Get Latest" class view and select "No" [to reload from file].

In trying to find a simple senario I ran across problems where additional messages were being added when "Get Latest" is run.    

If anyone knows of a work around or a fix, please let me know.