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 116893 - lifeline shifted below create message, java.lang.AssertionError is generated
Summary: lifeline shifted below create message, java.lang.AssertionError is generated
Status: RESOLVED WORKSFORME
Alias: None
Product: uml
Classification: Unclassified
Component: Diagram Sequence (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Craig Conover
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-27 00:18 UTC by George Vasick
Modified: 2007-10-05 00:25 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
screenshot (42.11 KB, application/octet-stream)
2007-09-27 00:19 UTC, George Vasick
Details
IDE log (4.98 KB, text/plain)
2007-09-27 00:20 UTC, George Vasick
Details
project zip (240.29 KB, application/octet-stream)
2007-09-27 00:22 UTC, George Vasick
Details
screenshot with corrected MIME type (42.11 KB, image/jpeg)
2007-09-27 00:23 UTC, George Vasick
Details

Note You need to log in before you can comment on or make changes to this bug.
Description George Vasick 2007-09-27 00:18:05 UTC
The lifeline for Observacao : WFRegistro02 is incorrectly displayed below the create message.  See attached screenshot,
IDE log, and project.
Comment 1 George Vasick 2007-09-27 00:19:11 UTC
Created attachment 49625 [details]
screenshot
Comment 2 George Vasick 2007-09-27 00:20:32 UTC
Created attachment 49626 [details]
IDE log
Comment 3 George Vasick 2007-09-27 00:22:04 UTC
Created attachment 49627 [details]
project zip
Comment 4 George Vasick 2007-09-27 00:23:20 UTC
Created attachment 49628 [details]
screenshot with corrected MIME type
Comment 5 George Vasick 2007-09-27 00:24:45 UTC
Opened for mailto:fmcypriano@gmail.com
Comment 6 Craig Conover 2007-10-02 04:46:36 UTC
There are some odd things going on due to the model not showing up. Perhaps my project zip file has a corrupted project
metadata? I can not reliable work with the diagram because it deletes itself after I open it once and then I get NPE's
when I click on any node.

George, do you see any nodes under the Model root node?

"fmcypriano", Can you explain how you got into this scenario? Did you RE the operation, or create diagram by hand?

Comment 7 fmcypriano 2007-10-02 12:23:25 UTC
I've do this by hand.

I started the project in Netbeans 5.5.1 and always they put the object below the create message. So, I test the NB6 b1
and the lines and objects started to appears in the right place, after a little use the problem started again even with
NB6 b1.
Comment 8 George Vasick 2007-10-02 19:30:11 UTC
Craig,

In response to your question, I do not see anything under the model node.  The model file is present in the project and
quite large, over 500 KB.  Something must be corrupted in the model.

George
Comment 9 Craig Conover 2007-10-03 19:35:39 UTC
From Felipe (customer)...

Using NB 5.5.1:
this issue always happens, for all the create messages and the targets.

Using NB 6 b1:
To test I start a new UML project from scratch. Added a sequence diagram and put some lifelines and only create messages
to new lifelines. With this test everything works fine (without problem with message and target).

So, I decide to open the project created in NB 5.5.1 and make the sequence diagram in NB6. When I started the diagram
the lines and targets were ok. Then, I keep doing the diagram making all the messages (not only the create messages).
When I make the create message from Ator to Observacao : WFRegristro2 the issue happens.

One thing that I was doing was deleting some elements in the diagram without checking the box "Deletion will permanently
delete elements from project". But, I don't no if this was the cause.
Comment 10 Craig Conover 2007-10-05 00:25:44 UTC
Felipe, none of us are able to reproduce and sounds like you are having trouble reproducing as well with your new
environment. Perhaps is was environmental. If you are able to reproduce again, and can give more precise steps and
environment details, please feel free to update this issue and reopen it.