JDK-5072943 : Code loaded by JNLPClassLoader should have CodeSource with correct codebase.
  • Type: Enhancement
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 6
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2004-07-12
  • Updated: 2004-12-21
  • Resolved: 2004-12-21
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 6
6Resolved
Related Reports
Duplicate :  
Description
In Java Web Start 1,5 and before, The CodeSource of code loaded by the JNLPClassLoader has the Codebase of the location in the cache where the code was loaded from.
This could be changed to have the Codebase be the URL of the resource on the net

In JNLPClassLoader, a findResource() returns a JAR url of a file url of the jar in the cache.
In Java Plug-in if you do a findResource() you get a JAR url into the jar on the net.

These should be made consistant.


Comments
EVALUATION for mustang we need to look into if we can fix this, or will it cause backwards compatibility problems. ###@###.### 2004-07-12 this is fixed as part of 4690736. The standard URLClassPath caused URLClassLoader to return entries from findResource(XXX) and getResource(XXX) as: "jar:URL!/XXX" where URL is now the original URL of the resource, not the file url into the cache. ###@###.### 2004-12-21 16:07:15 GMT
21-12-2004

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: mustang
31-08-2004