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.
Created attachment 140707 [details] OutputFromDebug Purpose: Test NetBeans FXML support. Setup: Java Platform 7u25 or 7u40 and JavaFX Scene Builder 1.1 GA installed. Netbeans 7.4 (any) Create New FXML Application in NetBeans Invoke File | New Project... from main menu. "New Project" wizard shows up. In the first step of the wizard select "JavaFX" category and "JavaFX FXML Application" project. Push Next > button. Keep all default settings and push Finish. In the Project View, Double-click on "FXMLDocument.fxml", which should open the selected FXML file in JavaFX Scene Builder 1.1 GA In Scene Builder, from the Library of Controls (upper left), drag a Button control onto the Anchor Pane next to the existing button. Click on the "Code" tab for this new Button control (bottom right) and the Code tab will expand. In the entry field for "fx:id" type: "Button2" and press enter. Save the file. Close Scene Builder. In NetBeans, right-click on "FXMLDocument.fxml" and click on "Make Controller", then click on Build. Next click the Debug (or Run) button. RESULT: The Project builds cleanly, but the Debug (or Run) fails. See attachment. REASON: See Bug 236509 and Bug 236559 (The fx:controller="javafxapplicationNN.FXMLDocumentController" property is then duplicated.) Environment: Product Version: NetBeans IDE 7.4 RC2 (Build 201309252201) Java: 1.7.0_40; Java HotSpot(TM) Client VM 24.0-b56 Runtime: Java(TM) SE Runtime Environment 1.7.0_40-b43 System: Windows 8 version 6.2 running on x86; Cp1252; en_US (nb)
Is blocked until bug 236509 fix becomes a 7.4 patch.
*** This bug has been marked as a duplicate of bug 236559 ***
Not exactly a duplicate of 236224, because while in this issue the FXML file is incapable of being loaded by the JavaFX Runtime, in Bug 236624 the issue is that the FXML file is incapable of being loaded in Scene Builder, Different issues, with the same cause: Bug 236509