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.
Build: NetBeans IDE Dev (Build 200709190000) VM: Java HotSpot(TM) Client VM, 1.6.0_02-b06 OS: Windows XP, 5.1, x86 User Comments: dbstuff
Created attachment 49524 [details] stacktrace
Build: NetBeans IDE Dev (Build 200710071200) VM: Java HotSpot(TM) Client VM, 1.6.0_03-b05 OS: Windows Vista, 6.0, x86 User Comments: Finishing Internationalization Wizard
Created attachment 50464 [details] stacktrace
Build: NetBeans IDE Dev (Build 200710071200) VM: Java HotSpot(TM) Client VM, 1.6.0_03-b05 OS: Windows Vista, 6.0, x86 User Comments:
Created attachment 50467 [details] stacktrace
Why is a NullPointerException P4? It seems to happen to me (JDK 1.6.0u3, Windows Vista) very often while using the Internationalization Wizard.
This issue has already 5 duplicates
most of the exceptions is coming from I18N wizard i18n.wizard.I18nWizardDescriptor.updateDefaultButton Reassigning for evaluation, maybe something can be done to get rid off the npe
Regarding the exceptions coming from the Internationalization Wizard, the cause is probably that the default button is set from a non-event-dispatching-thread (aka AWT thread) but from a request processor thread. The code is kind of weird - it tries to veto the change (just announced via listener) of the default button.
The weird part of code was introduced in revision 1.2 of file i18n/src/org/netbeans/modules/i18n/wizard/I18nWizardDescriptor.java Diff: http://deadlock.netbeans.org/fisheye/browse/netbeans/i18n/src/org/netbeans/modules/i18n/wizard/I18nWizardDescriptor.java?r1=1.1&r2=1.2
StackTrace: =========== java.lang.NullPointerException at java.util.Hashtable.get(Hashtable.java:334) at javax.swing.KeyboardManager.registerKeyStroke(KeyboardManager.java:86) at javax.swing.JComponent.registerWithKeyboardManager(JComponent.java:2168) at javax.swing.JComponent.registerWithKeyboardManager(JComponent.java:2093) at javax.swing.JComponent.componentInputMapChanged(JComponent.java:2163) at javax.swing.ComponentInputMap.put(ComponentInputMap.java:77)
The threading was changed in revision 1.3: http://deadlock.netbeans.org/fisheye/browse/netbeans/i18n/src/org/netbeans/modules/i18n/wizard/I18nWizardDescriptor.java?r1=1.1&r2=1.2
*** Issue 59436 has been marked as a duplicate of this issue. ***
*** Issue 122757 has been marked as a duplicate of this issue. ***
The solution is to rewrite the logic behind enabling/disabling the wizard buttons and switching the wizard step panels. There is plenty of custom code that most probably can be replaced with a few Dialogs API calls. It is too risky to do such rewrites that late in the NB 6.1 development cycle - I will fix it in the next release.
Build: NetBeans IDE Dev (Build 200803302302) 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:
Created attachment 59570 [details] stacktrace
I will fix it by removing all the hacks in the Internationalization module - I will use the standard API for wizards instead.
Fixed. Modified files: i18n/src/org/netbeans/modules/i18n/wizard/Bundle.properties i18n/src/org/netbeans/modules/i18n/wizard/HardStringWizardPanel.java i18n/src/org/netbeans/modules/i18n/wizard/I18nWizardDescriptor.java i18n/src/org/netbeans/modules/i18n/wizard/ResourceWizardPanel.java i18n/src/org/netbeans/modules/i18n/wizard/TestStringWizardPanel.java Mercurial changeset Id: 68776bfaf0bb (http://hg.netbeans.org/main/rev/68776bfaf0bb)
I am reopening it so that it can be passed to the 'db' module, which is the origin of the first reported exception.
Passed to the 'db' module so that the first reported exception can be resolved.
One of the exceptions originates in class org.netbeans.modules.jumpto.type.GoToTypeAction$Worker - see http://statistics.netbeans.org/analytics/detail.do?id=37751
I'm sorry, can you explain more what I need to do here? I've looked at the stack trace which calls ConnectionDialog.setVisible, and it appears that we are calling setVisible() on the AWT event thread. What do I need to do differently?
David, I do not see anything suspicious in the stack-trace either. So pass it to 'core' (maybe the bug is somewhere in the NbPresenter?) or to 'utilities/jumpto' so that the remaining issue in it gets fixed.
I am not sure I follow the thread of what is going on here, but re-assigning to core.
Integrated into 'main-golden', available in NB_Trunk_Production #206 build Changeset: http://hg.netbeans.org/main/rev/68776bfaf0bb User: mpetras@netbeans.org Log: fixed bug #116766 - "NPE i18n.wizard.I18nWizardDescriptor.updateDefaultButton"
David, please DO NOT assign to core issues that you don;t know what to do with. Core isn't your trash basket... I'm closing as fixed for now. The original exception should be fixed by mpetras commit. I cannot see anything connected with db here... Marian, please provide more details if you want to reassign to DB again
Lukas, apologies if you feel like a trash basket. As you can see from the history, I told Marian it didn't look like my issue, and Marian suggested I switch to core. I was just trying to get it to it's proper owner so it could get addressed. If this is not your bug, I don't believe it's appropriate for you to close the issue unless you are certain the issue is resolved. I'm not convinced it is, because Marian only fixed the issues in the Internationalization Wizard, and not the issue caused by the first stack trace. However, it does *not* belong to db, as it is clear from the stack trace that we are calling the setVisible() method from the AWT thread. I'll give it back to Marian so she can decide what to do with it.
For now, I am re-assigning it to module "Jump To". Once bug in "Jump To" is fixed, I will get back to the first exception.
Re bug in "Jump To": The exception's stack trace is at http://statistics.netbeans.org/analytics/detail.do?id=37751 The exception seems to have the same cause as the exception in the Internationalization module - enabling/disabling buttons from non-AWT thread. Moreover, I think that the GoToTypeAction should not create its own OK button - it should use a subclass of NotifyDescriptor.Message with OK_CANCEL_OPTION. Changes of state of the OK button can be achieved using a combination of overridden method 'isValid()' and changes of property PROP_VALID.
Jmupto issue was already fixed. http://hg.netbeans.org/main/rev/7abd17319461
I was trying to invoke that NPE, I was playing with with both Wizards and everything works correctly. Janie, please, can you test it too? Maybe all that bugfixes already fixed it. ;)
I tried i18n wizards as well and I cannot reproduce this exception as well. Seem to be fixed. tested on Product Version: NetBeans IDE Dev (Build 20081007071513) Java: 1.6.0_10-rc2; Java HotSpot(TM) Client VM 11.0-b15 System: Windows XP version 5.1 running on x86; Cp1252; en_GB (nb)
Seem to be fixed. (Tested by jvagner and janie)
v/c