![]() Double ugh!!!Īll this negativity was surmounted by a few interesting discoveries and a bit of careful thinking: Ugh! Or we could rewrite the existing fat client application, liked by its user community, as a web app. Option 2: Move away from JNLPĪt first, this approach seemed like the worst possible scenario-we would need to modify the application to provide configuration information in some other fashion all the nice automated-update stuff in JNLP would be discarded and we would need some kind of per-workstation installation process. Neither of these approaches seemed very appealing. However, Java SE 8 was reaching end-of-life in March 2019, so we would have to create a Java 8 runtime environment from OpenJDK 8 for installation on the client machines and move to a more manual process of tracking OpenJDK 8 updates. Unfortunately, when we were evaluating the options, there was not a working IcedTea-Web facility compatible with Java 11, so this would mean using Java 8. This would imply a two-step pre-configuration process: 1) install Java SE and 2) install IcedTea-Web, which would increase client-side maintenance. IcedTea-Web is an open source project that provides JNLP capabilities. Option 1: Stay with current Java SE and find a substitute for JNLP This relatively simple-sounding choice turned out to be somewhat complex for various reasons. However, because JNLP is no longer a part of Java SE (from version 11 onward), the organization was faced with a decision: discontinue its use of JNLP as a part of Java SE or eliminate its policy of staying reasonably up to date with Java SE releases. In other words, it was a nice, low-ceremony way to distribute a completely configured application to everyone's desktop. When they wanted to use the application, they would click on the link in the organization's intranet, and the Java Web Start ( javaws) program would download the XML at the link, interpret it, download the current version of the application if necessary, and run it, all while managing the security sandbox where the application ran. To access the Java Swing application, users had to install a specific version of Java Platform, Standard Edition (Java SE) that contained support for JNLP. ![]() For about the past 15 years, an organization I work with has used the Java Network Launching Protocol (JNLP) to internally distribute a Java Swing desktop application to its users. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |