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.
1. Ran a fresh install of Pilsen 010725_1 on Merlin (b73). 2. Selected Tools | Update Center. 3. Clicked on the Proxy Settings... button. 4. Closed the Proxy Settings dialog with Cancel. 5. Got the InvocationTargetException from property sheet (see attachment).
Created attachment 1981 [details] Exception stack-trace.
Adding the JDK_1.4 keyword, although I'm not sure the problem is specific to Merlin.
Seems like a problem in org.netbeans.modules.autoupdate.Settings.setAutoupdateType(Settings.java:115) If it is not there please reassign back (or to someone else).
It appears only on jdk1.4 (I tried on b73) Looks like problem in PropertyPanel, which calls setAutoupdateType( null ) Thread dump attached
Created attachment 1985 [details] Dump stack - calling setAutoupdateType( null )
The problem seems to be in PropertyDisplayer - will propose patch.
Created attachment 1988 [details] patch for PropertyDisplayer.java
Honza, should I request commit to Forte3.0/NetBeans 3.2.1? Is it serious enough bug?
*** Issue 14019 has been marked as a duplicate of this issue. ***
Not just JDK 1.4, if 14019 really is a duplicate issue; I was using JDK 1.3.1 when I got that (and the 3.2.1 RC1).
I am not able to reproduce this bug with the patch. I tested it with jdk1.4 and 1.3.1 and it looks that the problem is solved.
Passing to Petr ...
Marking as fixed since it is NB3.2/FFJ3.0 specific.
*** Issue 14871 has been marked as a duplicate of this issue. ***
Adjusting target milestone. The bug is not fixed in NB 3.2.1/FFJ 3.0.
Another way how it reproduce: [jdk1.4.0-b77, Forte 3.0 Build 010817] 1) expand popup Project > Settings > XML Settings > Default node ... (or Project>Settings>Corba Settings>J2EE ORB>Server Binding) 2) click on e.g. main window (the popu must be still expanded) IDE throws InvocationTargetException.
The bugfix is commited to {pilsenfixes}. It will go to the first FFJ 3.0 Jumbo Patch.
Sorry, but I have to reopen this issue. I installed whole JP3 and this was fixed in very strange way. The combo with 3 choices was replaced by the textfield with only one, so two options are left. Also the exception (which can be reproduced by M.Schovanek description) still persists.
*** Issue 15580 has been marked as a duplicate of this issue. ***
Seems like the strange behaviour was caused by the wrong updating process. With the patch from issue #15599 I do not see the described behaviour with the text field X combo box.
I also think that the patch was not applied properly due to bug #15599. I cannot reproduce it now. Marking as resolved fixed.
I cannot reproduce it when using JP3.1 - marking as verified.
*** Issue 16875 has been marked as a duplicate of this issue. ***
Resolved for 3.4.x or earlier, no new info since then -> closing.