JDK-6381718 : javaws import feature uses incorrect timestamp for jnlp file
  • Type: Bug
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 5.0u6
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2006-02-06
  • Updated: 2014-02-27
  • Resolved: 2006-05-03
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
5.0u8 b01Fixed
Description
when we do javaws import with alternatce codebase, the jnlp file timestamp we use is in the cache is incorrect.  we just store with the current system time during the import happens, but we should have used the last-modified date from the alternate codebase.

jar resources are okay, problem is only with jnlp file.

this exists in tiger only, mustang is okay.
Comments
SUGGESTED FIX http://web-east.east/deployment/www/webrevs/ngthomas/6381718/webrev/
25-03-2006
EVALUATION we should only store no href jnlp file using the current time. if the jnlp file has href, we should get the href last modified time instead.
25-03-2006