JDK-4979820 : cannot load class names containing some JSR 202 characters
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.net
  • Affected Version: 5.0
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2004-01-17
  • Updated: 2004-04-20
  • Resolved: 2004-04-06
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.0 b46Fixed
Related Reports
Duplicate :  
Relates :  
Relates :  
Relates :  
Description
JSR 202 relaxes the prior restrictions on the legal characters
in a class name. If you use some newly legal characters in a
class name such as the SPACE character or other characters which
must be escaped in the URL the class may be found.

For example, an applet class named "Fo o" (with a space between
the two 'o' characters) and an http codebase will result in
appletviewer attempting to fetch a file named "Fo".

This problem is not specific to appletviewer but applies to all
classes loaded through a URLClassLoader include applications
classes loaded through the "system class loader".

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: generic tiger-beta2 FIXED IN: tiger-beta2 INTEGRATED IN: tiger-b46 tiger-beta2
14-06-2004

EVALUATION Will fix for Tiger beta2.
11-06-2004

SUGGESTED FIX Change the class loading code to properly escape URLs created to fetch class files.
11-06-2004

PUBLIC COMMENTS Classes using newly legal class name syntax relaxed by JSR 202 may fail to be found and loaded.
10-06-2004