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.
Product Version: NetBeans IDE Dev (Build 080208) Java: 1.6.0_04; Java HotSpot(TM) Client VM 10.0-b19 System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb) Userdir: C:\Documents and Settings\Lukas\.netbeans\dev The exception appeared when I wanted add server (Local Default Domain) second time INFO [org.openide.WizardDescriptor] java.io.IOException: Could not create instance. at org.netbeans.modules.j2ee.sun.ide.j2ee.ui.AddDomainWizardIterator.instantiate(AddDomainWizardIterator.java:303) at org.netbeans.modules.j2ee.deployment.impl.bridge.BridgingServerWizardProvider$InstantiatingIteratorBridge.instantiate(BridgingSer verWizardProvider.java:97) at org.netbeans.modules.server.ui.wizard.AddServerInstanceWizard$AddServerInstanceWizardIterator.instantiate(AddServerInstanceWizard .java:279)
Created attachment 56461 [details] stacktrace
instantiate is implemented as http://bits.netbeans.org/dev/javadoc/org-openide-dialogs/org/openide/WizardDescriptor.InstantiatingIterator.html#instantiate() dictates.... I don't know why somebody decided to print the exception at INFO level in the log... I will take a deeper look at this
looks like WizardDescriptor.java is the one sending this message out at INFO... See WizardDescriptor.java (line 1913)
I don't see any problem here. If a API user implementation of WD.II.instantiate() throws some IOException, wizard infrastructure logs it as INFO for tracking a problem later. It's intentional. The only question is why AddDomainWizardIterator.instantiate() is called in that case of duplicate server what was caught before. IMHO the Add Server wizard should not call instantiate() in that case.
How do I indicate that instantiate fails? http://bits.netbeans.org/dev/javadoc/org-openide-dialogs/org/openide/WizardDescriptor.InstantiatingIterator.html#instantiate() Do I: 1. return an empty set 2. return null 3. throw an IOException
I cannot stop the lower layer from logging an exception that the documentations says it may have to catch.