JDK-4213486 : (1.1) JDK118[Sol] Error msg is different from 1.1.7 when loading Japanese class
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 1.1.8
  • Priority: P4
  • Status: Closed
  • Resolution: Won't Fix
  • OS: solaris_2.6
  • CPU: sparc
  • Submitted: 1999-02-22
  • Updated: 2001-10-25
  • Resolved: 2001-10-25
Related Reports
Relates :  
Relates :  
Description
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.

Comments
EVALUATION This bug has been closed as "Will Not Fix" due to a strategic redirection of resources to Java 1.4. If bug needs to be fixed in an old release then an escalation will need to be filed. At that time the JPSE will take this bug over. Bugs which are escalations from external customers will continue to be addressed by the support team. Internal customers may escalate bugs by filing them as priority 1 (P1) bugs. ###@###.### 2001-10-25
25-10-2001