Javalobby - Comments for "Obtaining an Array class with Java reflection"

ClassLoaders aren't required

jyrinx — Wed, 02 Apr 2008 21:17:13 -0400

ClassLoaders aren't required to support the syntax at all. I'm guessing you were calling the ClassLoader directly?

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6500212

The three-argument form of Class.forName is the way to go if you need to use a particular ClassLoader, as I understand. (Though your reflection call works just as well, I imagine. What's a zero-length array instantiation among friends? :-) )

Hello Alex, I remembered

onur_ersen — Thu, 13 Mar 2008 06:00:07 -0400

Hello Alex,

I remembered that I read some information about reflections and arrays as you've mentioned.I found the article that I read among sun developer documents.

http://java.sun.com/developer/technicalArticles/ALT/Reflection/

Hope it also helps to those really wondering what you are trying to tell about java reflection,creating instances dynamically & arrays.

Regards,

ONur.

There is another catch with

eu — Wed, 12 Mar 2008 18:11:29 -0400

There is another catch with class literals. If there are class loaders involved, you may not always get the Class instance you are looking for, because .class instance is created using caller classloader, which can be not the same during instance initialization... Though this is quite advanced case. :-)

Yep - I forgot that I

puredanger — Wed, 12 Mar 2008 15:49:05 -0400

Yep - I forgot that I actually started with this but wanted to avoid the instance creation.

I've run into ClassLoaders

bl92550 — Wed, 12 Mar 2008 15:35:21 -0400

I've run into ClassLoaders which didn't support using forName() like that.

Here's another approach:

Class<?> elementType = ...;

Class<?> arrayType = Array.newInstance(elementType, 0).getClass();