[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: A query on the classloader architecture
From: |
Chris Gray |
Subject: |
Re: A query on the classloader architecture |
Date: |
Mon, 12 Jul 2004 10:26:25 +0200 |
User-agent: |
KMail/1.5.4 |
On Monday 12 July 2004 00:57, David Holmes wrote:
> Hmmm. Given that the *only* distinction between the two forms of forName
> are that the first implies initialize=true while the latter gives
> initialize=false, I don't know why anyone would write that code. ???
Oops, you're right; for some reason I thought the third parameter had to be
non-null. I should check the Java APIs before posting ...
OTOH there are times where you want to call a method (getPackage(),
findLibrary(), ...) of the appropriate classloader. Having a non-null
bootstrap class loader would help here.
--
Chris Gray /k/ Embedded Java Solutions
Embedded & Mobile Java, OSGi http://www.kiffer.be/k/
address@hidden +32 3 216 0369
- Re: A query on the classloader architecture, (continued)