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 225498

Summary: NullPointerException at org.netbeans.modules.form.layoutdesign.LayoutFeeder.addToGroup
Product: guibuilder Reporter: Exceptions Reporter <exceptions_reporter>
Component: CodeAssignee: issues@guibuilder <issues>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: P3    
Version: 7.3   
Hardware: All   
OS: All   
Issue Type: DEFECT Exception Reporter: 198153
Attachments: stacktrace

Description Exceptions Reporter 2013-01-29 23:41:25 UTC
This bug was originally marked as duplicate of bug 204815, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE 7.3 Beta 2 (Build 201211062253)
VM: Java HotSpot(TM) 64-Bit Server VM, 23.6-b04, Java(TM) SE Runtime Environment, 1.7.0_11-b21
OS: Linux

Stacktrace: 
java.lang.NullPointerException
   at org.netbeans.modules.form.layoutdesign.LayoutFeeder.addToGroup(LayoutFeeder.java:1311)
   at org.netbeans.modules.form.layoutdesign.LayoutFeeder.addInterval(LayoutFeeder.java:1179)
   at org.netbeans.modules.form.layoutdesign.LayoutFeeder.add(LayoutFeeder.java:470)
   at org.netbeans.modules.form.layoutdesign.LayoutDesigner.addComponents(LayoutDesigner.java:850)
   at org.netbeans.modules.form.layoutdesign.LayoutDesigner.endMoving(LayoutDesigner.java:811)
   at org.netbeans.modules.form.HandleLayer$ExistingComponentDrag.end(HandleLayer.java:2984)
Comment 1 Exceptions Reporter 2013-01-29 23:41:27 UTC
Created attachment 130803 [details]
stacktrace
Comment 2 Tomas Pavek 2014-02-07 15:26:03 UTC
This is the same exception as in bug 204815, but a different case, from a later version. The sample from the bug still works fine. Would be nice to have a new test case to reproduce this exception. It shows the layout structure blew up completely by moving (or adding) a component.
Comment 3 Tomas Pavek 2014-02-10 10:30:38 UTC
Actually the exception here indicates the same problem that in later versions is detected on a different place.

*** This bug has been marked as a duplicate of bug 240634 ***