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.
Create a loader in the wrong package, using the File Type template. Delete the loader files and the manifest entry, but *not* the layer mime resolver entry. Recreate the loader from template, this time in the correct package. Pressing Finish in the wizard updates the wizard error text with enigmatic content "Services/MIMEResolver/Fooresolver.xml" and the wizard does not exit. Three problems here: 1. The duplicate entry in the layer should be handled more gracefully, either by generating a different file name, or asking if the existing entry should be used 2. The wizard has not completed without error, but a lot of files have been generated - if a wizard fails it should not leave trash behind 3. The error text - the exception below is what's actually happening: INFORMATIONAL *********** Exception occurred ************ at 12:07 PM on Oct 9, 2005 java.io.FileNotFoundException: Services/MIMEResolver/Fooresolver.xml at org.netbeans.modules.apisupport.project.layers.WritableXMLFileSystem. outputStream(WritableXMLFileSystem.java:326) at org.openide.filesystems.StreamPool.createOutputStream(StreamPool.java :116) at org.openide.filesystems.AbstractFileObject.getOutputStream(AbstractFi leObject.java:196) at org.openide.filesystems.AbstractFileObject.getOutputStream(AbstractFi leObject.java:178) at org.netbeans.modules.apisupport.project.CreatedModifiedFilesFactory.c opyAndSubstituteTokens(CreatedModifiedFilesFactory.java:220) at org.netbeans.modules.apisupport.project.CreatedModifiedFilesFactory.a ccess$100(CreatedModifiedFilesFactory.java:52) at org.netbeans.modules.apisupport.project.CreatedModifiedFilesFactory$C reateLayerEntry$1.run(CreatedModifiedFilesFactory.java:437) at org.netbeans.modules.apisupport.project.CreatedModifiedFilesFactory$L ayerModifications.run(CreatedModifiedFilesFactory.java:503) at org.netbeans.modules.apisupport.project.CreatedModifiedFilesFactory$C reateLayerEntry.run(CreatedModifiedFilesFactory.java:481) at org.netbeans.modules.apisupport.project.CreatedModifiedFiles.run(Crea tedModifiedFiles.java:145) at org.netbeans.modules.apisupport.project.ui.wizard.loader.NewLoaderIte rator.instantiate(NewLoaderIterator.java:64) at org.openide.loaders.TemplateWizard$InstantiatingIteratorBridge.instan tiate(TemplateWizard.java:949) at org.openide.loaders.TemplateWizard.handleInstantiate(TemplateWizard.j ava:537) at org.openide.loaders.TemplateWizard.instantiateNewObjects(TemplateWiza rd.java:376) at org.openide.loaders.TemplateWizardIterImpl.instantiate(TemplateWizard IterImpl.java:218) at org.openide.WizardDescriptor.callInstantiate(WizardDescriptor.java:11 83) at org.openide.WizardDescriptor.access$1300(WizardDescriptor.java:70) [catch] at org.openide.WizardDescriptor$Listener$2.run(WizardDescriptor.java:162 5) at org.openide.WizardDescriptor.lazyValidate(WizardDescriptor.java:1147) at org.openide.WizardDescriptor.access$900(WizardDescriptor.java:70) at org.openide.WizardDescriptor$Listener.actionPerformed(WizardDescripto r.java:1652) at sun.reflect.GeneratedMethodAccessor383.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25)
Re. #1 - will investigate at some point. May be dupe. Re. #2 - no. There is no transactionality support in Filesystems. Re. #3 - will investigate; the message is OK but I don't know what code would be putting it in the wizard. (Was not marked human displayable.)
I can reproduce a different problem (AssertionError) in current dev builds. Not sure exactly what is going on but probably not too complicated.
Not into 7.0 or next release. Feel free to reopen if more important than it seems.
A mistake, sorry.
This bug was reported against NetBeans IDE 6.0 or an older release, or against a non-maintained module. NetBeans team does not have enough resources to get to this issue, therefore we are closing the issue as a WONTFIX. If you are interested in providing a patch for this bug, please see our NetFIX guidelines for how to proceed. We apologize for any inconvenience. Thank you. The NetBeans Team