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.
Summary: | NullPointerException at java.awt.Rectangle.<init> | ||
---|---|---|---|
Product: | uml | Reporter: | chcornwell <chcornwell> |
Component: | General Diagram | Assignee: | issues@uml <issues> |
Status: | NEW --- | ||
Severity: | blocker | CC: | pierocavalieri, seongdo, tomasmalmsten, Viscacha, zaad |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://statistics.netbeans.org/exceptions/detail.do?id=11610 | ||
Issue Type: | DEFECT | Exception Reporter: | 11610 |
Attachments: |
stacktrace
Sample project with same sequence structure as one reported. |
Description
chcornwell
2009-04-07 16:44:07 UTC
Created attachment 79661 [details]
stacktrace
Probably Scene.validate() was not called after last change. Can anybody attach project with "saved sequence diagram"? let's evaluate in mobility first 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 Created attachment 80629 [details]
Sample project with same sequence structure as one reported.
Looks like Visual Lib issue, reassigning. This issue already has 22 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=11610 Last reports from 6.7, mentioning UML. Not a general problem of platform/graph but a problem of the use in UML. |