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 184955 - NullPointerException at org.netbeans.modules.javafx.composer.properties.Installer$2.run
Summary: NullPointerException at org.netbeans.modules.javafx.composer.properties.Insta...
Status: RESOLVED FIXED
Alias: None
Product: javafx
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: David Kaspar
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-26 08:58 UTC by piotrk2007
Modified: 2010-05-12 16:25 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 168615


Attachments
stacktrace (819 bytes, text/plain)
2010-04-26 08:58 UTC, piotrk2007
Details

Note You need to log in before you can comment on or make changes to this bug.
Description piotrk2007 2010-04-26 08:58:20 UTC
Build: NetBeans IDE 6.9 Beta (Build 201004200117)
VM: Java HotSpot(TM) Client VM, 1.6.0_02-b06, Java(TM) SE Runtime Environment, 1.6.0_02-b06
OS: Windows XP

User Comments:
piotrk2007: New Project : JavaFX DesktopApplication




Stacktrace: 
java.lang.NullPointerException
   at org.netbeans.modules.javafx.composer.properties.Installer$2.run(Installer.java:90)
   at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
   at java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
   at org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:133)
   at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273)
   at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183)
Comment 1 piotrk2007 2010-04-26 08:58:30 UTC
Created attachment 98001 [details]
stacktrace
Comment 2 Lukas Hasik 2010-04-26 09:33:27 UTC
from the messages. log it seems more like problem with the installation. Could you try to uninstall-install again?

Cannot load org.netbeans.modules.javafx.project.ui.wizards.Bundle for MultiFileObject@334ba0[Templates/Project/JavaFX/emptyJavaFX.xml] defined by [jar:file:/C:/Program%20Files/NetBeans%206.9%20Beta/javafx/modules/org-netbeans-modules-javafx-project.jar!/org/netbeans/modules/javafx/project/layer.xml]
Caused: java.util.MissingResourceException: No such bundle org.netbeans.modules.javafx.project.ui.wizards.Bundle
	at org.openide.util.NbBundle.getBundle(NbBundle.java:443)
	at org.openide.util.NbBundle.getBundle(NbBundle.java:375)



INFO [org.netbeans.core.startup.layers.BinaryFS]: value = org.netbeans.modules.javafx.platform.platformdefinition.PlatformConvertor.createProvider from xml/lookups/NetBeans/DTD_JavaFX_PlatformDefinition_1_0.instance
java.lang.ClassNotFoundException: org.netbeans.modules.javafx.platform.platformdefinition.PlatformConvertor
	at java.net.URLClassLoader$1.run(URLClassLoader.java:200)


INFO [org.netbeans.core.startup.layers.BinaryFS]: value = org.netbeans.modules.java.j2seplatform.libraries.J2SELibraryTypeProvider.create from org-netbeans-api-project-libraries/LibraryTypeProviders/j2se_library_provider.instance
java.lang.ClassNotFoundException: org.netbeans.modules.java.j2seplatform.libraries.J2SELibraryTypeProvider
	at java.net.URLClassLoader$1.run(URLClassLoader.java:200)


these exception are definitelly weird.

Any steps to reproduce it?
Comment 3 David Kaspar 2010-04-28 12:15:01 UTC
The NPE is caused by not-found FxPropertiesGroup TCGroup. This is weird since this group is defined in the mf-layer.xml in the module. The code is invoke in SwingUtilities.invokeLater which is invoked from ModuleInstall.restored method. I assume that at that moment, all data from layer should be recognized/loaded/known already.

Therefore it seems that there is:
1) a bug in Module System or Window System or
2) the IDE has not be installed correctly or
3) the .netbeans user-directory is corrupted.

Anyway to prevent the NPE, I have added a code to check for not-found TCGroup. If the TCGroup is not found then the Properties window will not automatically open/close, so an user would have to manage it manually.

Relsoving as Fixed.
Comment 4 David Kaspar 2010-05-12 16:25:02 UTC
Newer/Improved fixed has been integrated which uses WindowManager.getDefault().invokeWhenUIReady method to ensure that Window-System is up and running.