JDK-8162858 : Allow to use high-resolution splash screens in webstart
  • Type: Enhancement
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 9
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2016-08-01
  • Updated: 2018-03-23
  • Resolved: 2018-03-23
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 8
8-poolFixed
Related Reports
Relates :  
Description
There is a way to define a splash screen in Java webstart app. 
https://blogs.oracle.com/thejavatutorials/entry/changing_the_java_web_start
<icon href="mysplash.jpg" kind="splash"/>

It should be possible to provide high-resolutions splash screens for HiDPI displays:
---------
mysplash.jpg
mysplash@125pct.jpg
mysplash@150pct.jpg
mysplash@2x.jpg
---------

The proposed name convention for splash screens: @125pct @150pct @2x @250pct @3x

See JDK-8151787 Unify the HiDPI splash screen image naming convention
Comments
Will not be fixed for JDK 8. Reopen if anyone find this is still an issue that need to be fixed.
23-03-2018

since JDK9 the javaws splash screen mechanism uses only the "-splash:<file-path>" java arg mechanism, but the <file-path> is a path into the deployment cache where the file has been downloaded from the net as directed by the jnlp file on the first run. In order to let the awt mechanism handle this, we would need to both download all resolutions of a specified splash image and place them in the cache using either their real name, or at least namine in conformance with JDK-8151787. Currently cache entries are obfuscated such as: C\:\\Users\\aherrick.ORADEV\\AppData\\LocalLow\\Sun\\Java\\Deployment\\cache\\6.0\\48\\62e24430-154f826d Alternatively, we could download only the "best fit" for the current resolution, though this would have unexpected results when the screen resolution changed between runs. Either type of implementation would require us to either probe the net for alternate resolutions of the given splash image, or change to jnlp spec to allow specification of multiple splash images and their resolutions.
15-02-2017