fxlauncher: Unable to pass remote location to --app option
This will always cause a FileNotFoundException if a valid url is passed, leaving the only other option to use the --uri option.
This conflicts the README.MD description that you can pass the remote location into that option.
In my opinion the manifest loading is flawed. Instead of the --app and --uri params it should have --remote and --local params. We first try loading the remote manifest, if it succeeds sync the local manifest with the downloaded (if --local is used, of course). If it fails (no internet connection or --remote options wasn’t used) try loading the local manifest. If this fails too (deleted etc. or --local option wasn’t used) try loading the embedded manifest. If that fails (was never included) show error message to user.
As far as I understand, the project lacks a robust fallback design. This should solve it.
About this issue
- Original URL
- State: open
- Created 7 years ago
- Comments: 22 (8 by maintainers)
Hmm! OK, please post when you figure it out 😃
There is no such requirement, merely a suggestion if you think you need to move your app later, and don’t want to redeploy the application to do so. It’s no big deal using the aforementioned approach either though.
Yeah, the old server would have to stay available until all clients have done one update. But if you anticipate the need to change url down the line, just fix it once and for all by using a custom hostname for your application.
https://appname.yourdomain.com- if you ever need to change it, just point it to a new ip and you don’t need to mess around with FXLauncher at all.The
--appparameter is just a command line parameter to be able to override the url in the embedded app.xml manifest. You can always supply a new url in the remote manifest if you want to move the hosted artifacts later on.