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 162150 - NullPointerException at java.awt.Rectangle.<init>
Summary: NullPointerException at java.awt.Rectangle.<init>
Status: NEW
Alias: None
Product: uml
Classification: Unclassified
Component: General Diagram (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@uml
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-07 16:44 UTC by chcornwell
Modified: 2011-10-21 13:53 UTC (History)
5 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 11610


Attachments
stacktrace (6.50 KB, text/plain)
2009-04-07 16:44 UTC, chcornwell
Details
Sample project with same sequence structure as one reported. (231.10 KB, application/octet-stream)
2009-04-21 20:28 UTC, chcornwell
Details

Note You need to log in before you can comment on or make changes to this bug.
Description chcornwell 2009-04-07 16:44:07 UTC
Build: NetBeans IDE 6.5 (Build 200811100001)
VM: Java HotSpot(TM) Client VM, 10.0-b19, Java(TM) SE Runtime Environment, 1.6.0_04-b12
OS: Windows XP, 5.1, x86

User Comments:
GUEST: Trying to use a Via...

chcornwell: Attempting to open a previously saved UML Sequence Diagram.

GUEST: I was running a web project using JSF. Netbeans freezes indefinately, 3 times a day from 8 hours of work.

r_ruba: J2ME FLOW Designer:
Try to create a connection between 2 function via an alert.

GUEST: was just opening previously saved sequence diagram

GUEST: There is an Exception thrown everytime I forward a call to a form via an alert from an if statement.

Regards,
mandla.ngcobo@gmail.com



Stacktrace: 
java.lang.NullPointerException
        at java.awt.Rectangle.<init>(Rectangle.java:179)
        at org.netbeans.api.visual.widget.Widget.paintBorder(Widget.java:1448)
        at org.netbeans.api.visual.widget.Widget.paint(Widget.java:1412)
        at org.netbeans.api.visual.widget.Widget.paintChildren(Widget.java:1472)
        at org.netbeans.api.visual.widget.Widget.paint(Widget.java:1420)
        at org.netbeans.api.visual.widget.Widget.paintChildren(Widget.java:1472)
Comment 1 chcornwell 2009-04-07 16:44:12 UTC
Created attachment 79661 [details]
stacktrace
Comment 2 t_h 2009-04-14 15:00:44 UTC
Probably Scene.validate() was not called after last change.
Comment 3 Sergey Petrov 2009-04-14 16:02:54 UTC
Can anybody attach project with "saved sequence diagram"?
Comment 4 Sergey Petrov 2009-04-15 11:07:55 UTC
let's evaluate in mobility first
Comment 5 chcornwell 2009-04-21 20:24:30 UTC
Sorry, I mangled the project with the problematic diagram and I am now unable to reproduce the behavior. I am attaching
a new project (created with Build 200811100001) with the same sequence diagram except for the my_controller timeline as
noted below. Several things I've noticed:
- The problem diagram was copied and renamed, so that it was cross-linked with the original diagram (which only
contained timelines, no messages)
- The problem diagram had multiple messages originating from a single timeline. With one exception I am no longer able
to create more than one transaction on an active segment. The exception appears in the attached project - the render
message from my_controller to listing:View was created following the void return from init_queue_element. When the
diagram was reloaded after closing the project and restarting Netbeans, that message is placed between the
init_queue_element message and its return.

The attachment contains saved snapshots of the project at key points during diagram creation. The version tagged
_gettingFlaky is beginning to exhibit some of the odd behavior of the original. Hope this helps.

- Carl
Comment 6 chcornwell 2009-04-21 20:28:00 UTC
Created attachment 80629 [details]
Sample project with same sequence structure as one reported.
Comment 7 Karol Harezlak 2009-04-24 10:26:03 UTC
Looks like Visual Lib issue, reassigning.
Comment 8 Exceptions Reporter 2009-07-01 15:40:07 UTC
This issue already has 22 duplicates 
see http://statistics.netbeans.org/exceptions/detail.do?id=11610
Comment 9 Antonin Nebuzelsky 2011-10-21 13:53:23 UTC
Last reports from 6.7, mentioning UML. Not a general problem of platform/graph but a problem of the use in UML.