JDK-8116930 : SceneBuilder is not dealing well with classpath relative URLs.
- Type: Bug
- Component: javafx
- Sub-Component: tools-scenebuilder
- Affected Version: 7u6
- Priority: P4
- Status: Resolved
- Resolution: Duplicate
- Submitted: 2012-06-22
- Updated: 2015-06-17
- Resolved: 2013-12-26
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 8 |
|---|
8Resolved  |
Related Reports
|
Duplicate :
|
Description
If an FXML contains a classpath relative URL, e.g. something like <Image url="@/my/image.png"/> or <fx:include source="/my/include.fxml"/> it might not load in scenebuilder. If it does load e.g. because there were unknown types and the user managed to specify a classpath, then the urls might not be preserved correctly.