I agree with jmaasing. Oracle and the JogAmp community are independent. Oracle has its own agenda. I advise you to read what I wrote in the wiki:
http://jogamp.org/wiki/index.php/Java3D_OverviewThe situation in OpenJFX/JavaFX isn't the same as the situation in Swing and AWT. The former doesn't have a stable public API to communicate with its native part and with its windowing toolkit (named Glass) whereas the latter has JAWT:
http://docs.oracle.com/javafx/2/architecture/jfxpub-architecture.htmAs a consequence, it's easier to interoperate with Swing and AWT than with OpenJFX/JavaFX. This problem doesn't affect only Java3D, it affects JOGL itself:
https://jogamp.org/bugzilla/show_bug.cgi?id=607OpenJFX/JavaFX has its own rendering pipeline.
Oracle plans to create an "OpenGLNode" to ease the use of third party libraries to perform OpenGL rendering but it's not ready yet.
In my humble opinion, OpenJFX/JavaFX 3D is a lot less capable than many third party libraries. If you really want to use OpenJFX/JavaFX with Java3D, you can try to put a Canvas or a JCanvas into an OpenJFX/JavaFX SwingNode. If it doesn't work, you'll have to choose between OpenJFX/JavaFX + OpenJFX/JavaFX 3D and Swing/AWT + Java3D.