Best practice for JavaFX lifecycle when not used as a normal application

Question

Suppose there was a Java app that runs in a terminal with its own command line interface. Certain commands typed in would show a Window that contains a Stage/Scene. In order to accomplish this, I would call Application.launch( App.class, null );. The problem is this Window may be closed by the User and then a future command may bring up another Window. As we know Application.launch may only be called one. Also the launch method blocks the calling thread.
Naively I would create an adapter that spawns a thread on the initial call to call Application.launch for the first window and bypass this for future windows.
Though if someone has an understanding of the best way to go about spawning arbitrary Scenes from an app where the app lifecycle is at a larger scale than javafx.application.Application that would be most appreciated.

Answer 1

In this situation, there isn't really a "primary" stage but an initial one. I can hook up a thread to call Application.launch and instrument it so the Stage it creates (and calls start on) is handled and additional stages will bypass Application.launch and create new Stages.
But this feels like a kludge to me.
I wonder if there is a different way to get the Toolkit operating in the background. This would be similar, I suppose, to how calling setScene on JFXPanel works.
Ideas anyone?