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.
Sent for review:
http://cr.openjdk.java.net/~anthony/8-62-headlessAppDelegate-7159266.0/
http://mail.openjdk.java.net/pipermail/awt-dev/2013-October/005893.html
04-10-2013
We still don't need to set an ApplicationDelegate in the headless mode, hence the fix needs to be forward-ported anyway. As to the inability to run with j2d currently, well, that's unfortunate since I can't verify this fix. But currently this looks more like an FX issue completely unrelated to the ApplicationDelegate (btw, is there a JIRA filed for the j2d issue?).
Anyway, since the fix is simple and has already been verified in 7u4, I think we're fine to go.
04-10-2013
moved back to main bug Assignee
28-08-2013
We cannot simply forward port the fix for the parent CR because we do not set awt to headless node for JDK-8, so it would not help anyway. I am not sure is it is an intensional behavior.
Additionally, there is a deadlock on an JavaFX application startup with J2D pipeline. Appkit thread locks in PaintCollector.waitForRenderingToComplete and QuantumRenederer locks in CGraphicsDevice initialization which makes synchronous calls to the Appkit thread.
I am not sure yet whether this issue should be fixed in JDK or in JavaFX.