When saving an activity diagram that contains an exception widget, its shape changes from that resembling a lightening bolt to something seemingly arbitrary. Reproducible: Always Steps to Reproduce: 1. Create a new activity diagram 2. Add two normal activity widgets with an exception widget between 3. Save and close the file. Actual Results: The shape of the exception widget changes Expected Results: The shape of the exception widget should not change
3. Save, close and reopen the file....
Created attachment 88661 [details] XMI file with actictivity diagram including an exception transition I tried reproducing the behavior with this file, by moving around the branch and the activity to different positions, each time saving and loading - but the exception looks okay to me. Could you attach an XMI which exhibits the problem? Thanks.
Created attachment 88670 [details] Activity diagram after create, save, close and load cycle
I tried the attachment you uploaded and it rendered fine.
Created attachment 88676 [details] Screen capture showing the described behaviour
I wonder if there might be a generic problem with my system since i see a lot of strange behavior that i would expect resulted in more bugs been filed (i looked through most of the open bugs). But i do see the same behavior on the two gentoo boxes i use on a daily basis.
I found a case where after the save/load cycle the start and end line of the exception association widget are not in parallel. Also I'm also able to reduce the exception to a simple line without any arror displayed if I reduce the distance of the two activities.
(In reply to Ralf Habacker from comment #7) > I found a case where after the save/load cycle the start and end line of the > exception association widget are not in parallel. Also I'm also able to > reduce the exception to a simple line without any arror displayed if I > reduce the distance of the two activities. Looks like an implementation issue of the exception drawing.
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.