-
Bug
-
Resolution: Won't Fix
-
P4
-
None
-
1.1.8
-
sparc
-
solaris_2.6
Can't loading a class whose name includes a character outside the
standard 7bit ASCII set is a known bug. See also 4193134.
When loading the class that includes Japanese, we got the following
error messages in the previous version in our testing.
% java ɽ½½É½
^^^^^^
Japanese Kanji
Can't find class ɽ½½É½
^^^^^^
Japanese Kanji
In JDK1.1.8 build "H" on Solaris Only, the error messge is changed.
Error loading class ɽ½½É½: Wrong name
^^^^^^
Japanese Kanji
On Windows NT with build "H", I can see still the same as "Can't find class".
JDK1.1.7 (Solaris, Win32) : Can't find class ɽ½½É½
JDK1.1.8H (Win32) : Can't find class ɽ½½É½
JDK1.1.8H (Solaris) : Error loading class ɽ½½É½
I'm not sure that this is a bug or not, because I don't know the functinal
spec on this case. However I think the error message shoule be the same
both on Solaris and Win32.
Tested Environment:
Solaris 2.6 on SPARC and Solaris 2.6 on Intel
iwabuchi@dandelion> java -fullversion
java full version "JDK1.1.8H"
I know that the impact is small, because a user can't load Japanese class
anyway even if the error message is different.
standard 7bit ASCII set is a known bug. See also 4193134.
When loading the class that includes Japanese, we got the following
error messages in the previous version in our testing.
% java ɽ½½É½
^^^^^^
Japanese Kanji
Can't find class ɽ½½É½
^^^^^^
Japanese Kanji
In JDK1.1.8 build "H" on Solaris Only, the error messge is changed.
Error loading class ɽ½½É½: Wrong name
^^^^^^
Japanese Kanji
On Windows NT with build "H", I can see still the same as "Can't find class".
JDK1.1.7 (Solaris, Win32) : Can't find class ɽ½½É½
JDK1.1.8H (Win32) : Can't find class ɽ½½É½
JDK1.1.8H (Solaris) : Error loading class ɽ½½É½
I'm not sure that this is a bug or not, because I don't know the functinal
spec on this case. However I think the error message shoule be the same
both on Solaris and Win32.
Tested Environment:
Solaris 2.6 on SPARC and Solaris 2.6 on Intel
iwabuchi@dandelion> java -fullversion
java full version "JDK1.1.8H"
I know that the impact is small, because a user can't load Japanese class
anyway even if the error message is different.
- relates to
-
JDK-4193134 (1.1) Problems loading classes named with non-English characters
- Closed
-
JDK-4094685 (i18n) The VM does not handle i18n issues related to class file names correctly
- Closed