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.
|Summary:||improve broken mappings between FXML files, controller and related resources detection|
|Component:||Editor||Assignee:||Svata Dedic <sdedic>|
|Issue Type:||ENHANCEMENT||Exception Reporter:|
Description pablopina 2014-05-17 08:56:10 UTC
Would be great if NB could highlight any broken references in FXML and controller classes such as -controller names -missing imports -relative urls in fxml file that do not resolve to an existing file (e.g. images, css files, etC) -wrong imports -elements annotated as @FXML which do not have a valid mapping (fx:id) in the FXML file and/or warnings for elements with a fx:id for which there is no component in the controller -wrong action methods (yai, this is done already) Would also be interesting to discuss whether these kind of errors should mark the project (in the projects view) as having errors. The one weakness i see in JSF or FXML is that there is no compilation of these files and very often errors are found at runtime. I saw how NB improved validation of EL expressions in JSF over time and it would be great if the same level of validation was applied to JavaFX development.