Issue 3590: loader.loadClass() or Class.forName()? (java2idl-rtf)
Source: Oracle (Mr. Bob Scheifler, rws(at)east.sun.com)
Nature: Uncategorized Issue
Severity: 
Summary: In 1.4.9.5, #4 of the Java 2 case:

4. If a class was not successfully loaded by step 1, 2, or 3, and loader is
   non-null, then call loader.loadClass(className)

Shouldn't that really be Class.forName(className, false, loader), so that
array types are handled properly?

ClassLoader.loadClass does not handle creating new array types (it
will only find previously created array types), Class.forName does.

Resolution:  See revised text below.
Revised Text: n 1.4.9.5, replace #4 of the Java 2 case by: 

4. If a class was not successfully loaded by step 1, 2, or 3, and loader is

   non-null, then call Class.forName(className, false, loader).
Actions taken:
May 2, 2000: received issue
May 24, 2001: closed issue
Discussion: 

End of Annotations:=====
Date: Mon, 01 May 2000 22:43:14 +0100
From: Simon Nash <nash@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.72 [en] (Windows NT 5.0; I)
X-Accept-Language: en
MIME-Version: 1.0
To: issues@omg.org
CC: java2idl-rtf@omg.org
Subject: loader.loadClass() or Class.forName()?
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
X-UIDL: Mg,!!GRH!!%=&e9IPK!!

The following issue was raised by Bob Scheifler of Sun.

In 1.4.9.5, #4 of the Java 2 case:

4. If a class was not successfully loaded by step 1, 2, or 3, and
   loader is
   non-null, then call loader.loadClass(className)

Shouldn't that really be Class.forName(className, false, loader), so
that
array types are handled properly?

ClassLoader.loadClass does not handle creating new array types (it
will only find previously created array types), Class.forName does.

   Simon
-- 
Simon C Nash, Technology Architect, IBM Java Technology Centre
Tel. +44-1962-815156   Fax +44-1962-818999    Hursley, England
Internet: nash@hursley.ibm.com   Lotus Notes: Simon Nash@ibmgb