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 216599 - NullPointerException at java.awt.Container.addImpl
Summary: NullPointerException at java.awt.Container.addImpl
Status: RESOLVED DUPLICATE of bug 127881
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 7.2
Hardware: All All
: P3 normal (vote)
Assignee: issues@guibuilder
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-09 13:07 UTC by Michel Graciano
Modified: 2012-08-17 16:52 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 191423


Attachments
stacktrace (4.55 KB, text/plain)
2012-08-09 13:07 UTC, Michel Graciano
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michel Graciano 2012-08-09 13:07:18 UTC
This bug was originally marked as duplicate of bug 166092, 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.2 (Build 201207101812)
VM: Java HotSpot(TM) 64-Bit Server VM, 22.1-b02, Java(TM) SE Runtime Environment, 1.7.0_03-b05
OS: Windows 7

Stacktrace: 
java.lang.NullPointerException
   at java.awt.Container.addImpl(Container.java:1086)
   at java.awt.Container.add(Container.java:410)
   at org.netbeans.modules.form.layoutdesign.support.SwingLayoutBuilder.createLayout(SwingLayoutBuilder.java:171)
   at org.netbeans.modules.form.layoutdesign.support.SwingLayoutBuilder.setupContainerLayout(SwingLayoutBuilder.java:108)
   at org.netbeans.modules.form.VisualReplicator.setupContainerLayout(VisualReplicator.java:822)
   at org.netbeans.modules.form.VisualReplicator.cloneComponent(VisualReplicator.java:754)
Comment 1 Michel Graciano 2012-08-09 13:07:20 UTC
Created attachment 122933 [details]
stacktrace
Comment 2 Tomas Pavek 2012-08-17 16:52:41 UTC
Looks like it's due to the problem with classloaders described in bug 127881 (where also a workaround is mentioned).

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