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 8.0 (Build 201403101706) VM: Java HotSpot(TM) 64-Bit Server VM, 25.0-b70, Java(TM) SE Runtime Environment, 1.8.0-b132 OS: Windows 8 User Comments: skiwi: I simply wanted to create an FXML file via the wizard in a source package, however then this error came up. Stacktrace: java.lang.IllegalArgumentException: Called DataObject.find on null at org.openide.loaders.DataObject.find(DataObject.java:551) at org.openide.loaders.DataFolder.findFolder(DataFolder.java:540) at org.netbeans.modules.javafx2.project.fxml.FXMLTemplateWizardIterator.instantiate(FXMLTemplateWizardIterator.java:214) at org.openide.loaders.TemplateWizard$InstantiatingIteratorBridge.instantiate(TemplateWizard.java:1046) at org.openide.loaders.TemplateWizard.handleInstantiate(TemplateWizard.java:605) at org.openide.loaders.TemplateWizard.instantiateNewObjects(TemplateWizard.java:439)
Created attachment 147551 [details] stacktrace
Thanks for the report, however I am not able to reproduce the issue, could you please write more detailed steps how to reproduce it? Can you reproduce it repeatedly? Thanks.
I'm sorry, I hoped it would be a trival bug to find. I am unable to reproduce the bug myself anymore either. I created the project as standard Java application, then did a whole array of actions over time, and then wanted to add an FXML via the Wizard obtained after right-clicking a package and creating New File. One difference I do notice between my version and the newly created working project is the following: - In my project it was forcing the FXML to be under the Resources package, whereas in new projects it is under the source packages. - In my project in the path to the file there was a <Project Resources> placeholder.
Thanks for the explanation. Since we are unable to reproduce the issue I am closing this as "works for me" for now. If you will be able to reproduce the problem, please reopen this issue with steps how to reproduce it. Thanks!