Currently, the ExampleServerLauncher (From the Workflow example) only needs a synchronous/blocking implementation of the ServerLauncher. Once the ServerLauncher is running, it runs in an infinite loop and there is no way to stop it (Other than killing the application)
Providing an asynchronous & stoppable implementation of this class would be helpful (Say, if the server is meant to be embedded in an Eclipse application :) )
Currently, the ExampleServerLauncher (From the Workflow example) only needs a synchronous/blocking implementation of the ServerLauncher. Once the ServerLauncher is running, it runs in an infinite loop and there is no way to stop it (Other than killing the application)
Providing an asynchronous & stoppable implementation of this class would be helpful (Say, if the server is meant to be embedded in an Eclipse application :) )