JDK-6953922 : JNLP application can't find and load resource (txt file) from its application jar file
  • Type: Bug
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 5.0u25
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2010-05-19
  • Updated: 2014-03-25
  • Resolved: 2010-06-18
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.
Other
1.4.2_37Fixed
Related Reports
Relates :  
JDK-6767754 - remove the JNLPURLStreamHandler class from jaws code and follow 6.0 coding pattern
Relates :  
JDK-6340856 - Classloader is unable to load classes from extension jars (premature close)
Description
Short desc:
  javaws testsuite test "update" fails when tries to load info.txt file
  which is located inside application jar.

  The same code works OK if it is executed as standalone java app/class
  without using javaws.

See "Comments" section for details.
Comments
EVALUATION The jar version request needs to be sent in the DownloadProtocol.getCachedVersion of JNLPCachedJarURLConnection.connect to ensure that the correct jar version is loaded into cache. A new helper method is required in JNLPClassLoader to fix this. The new HashMap will store the relationship between jar version and original URL at load time. Versioning tests documented in this bug report passing with fix. New binary sent to the submitter for some sanity testing.
25-05-2010