从长字符串中提取java脚本中以“（/”开头，以“/）结尾”的特定字符串(extract a specific string which start with “(/ ” and ends with “/)” in java script from a long string)

 这里有很多问题。 
 
 1 - 使用fx：root允许您自定义FXMLLoader，您可以更改实例组件的方式： 如何使用不同的fxml文件创建多个javafx控制器？ 
 
 但是，使用SceneBuilder 2它根本不能正常工作！ 使用Scene Builder 2的“canonic”方式（与1一起正常工作）似乎不使用fx：root。 
 
 2 - 它取决于您在1中选择的模式。可以是FXML中的自定义Java组件，具有显式导入或使用fxml：include。 FXML首先是控制器。 或抽象组件（和控制器为fx：root）然后FXML。 
 
 3 - SceneBuilder 2对类加载器有很多麻烦，因为每个自定义组件都加载了一个不同的类加载器，这意味着你将运行很多类似于异常的类。 修复它的一种方法是将SceneBuilder派生用来强制它只为所有自定义组件使用一个类加载器： Scenebuilder 2.0中的自定义组件 
 
 或者等待修复。 或者不使用fx：root并且更喜欢fx：include。 或者根本不使用Scene Builder，这是许多有效的解决方案。 

Many questions here.
 
1 - Using fx:root allows you to customize FXMLLoader, you can change the way you instanciate components: How to create multiple javafx controllers with different fxml files?
 
But, with SceneBuilder 2 it does not work well at all! The "canonic" way with Scene Builder 2 (worked fine with 1) seems to NOT use fx:root.
 
2 - It depends on your pattern chosen in 1. Could be a custom java component in FXML with an explicit import, or using fxml:include. Either FXML first then controller. Or abstract component (and controller as fx:root) then FXML.
 
3 - SceneBuilder 2 has many troubles with classloaders as each custom component is loaded with a distinct class loader which means you'll run a lot with class not found like exceptions. One way to fix it is to fork SceneBuilder to force it using only one classloader for all custom components: Custom Components in Scenebuilder 2.0
 
Or wait for a fix. Or not using fx:root and prefering fx:include. Or not using Scene Builder at all which is for many a valid solution.