In Jaos, the ClassLoader is loaded but not really used (I'm still stuck with
classpath 0.5) because I have my own native implementation which overrides
the calls to Java's classloader in Class.fromName(). I'm currently upgrading
my implementation to work with 0.6 by moving all the native stuff into
gt; a java program.
>
> This remarks (in particular 2 and 3) are quite Jaos specific.
>
> This won't probably solve your problem, but may give you some insight about
> the various problems encountered during the initialization phase.
>
> -Patrik
>
> Patr
al Message -
From: "Joseph Wenninger" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, October 14, 2003 9:33 PM
Subject: classpath initialization
> Hi
>
> I'm trying to use an unmodified classpath (0.06). I already have
> something working with a m
Joseph,
> My problem is that the call stack during initialization of
> the System class I looks something like
...
> The last line causes an exception, since the static member
> properties isn't initialized yet.
Initialization is quite tricky. Basically your VMClassloader is making
assumptions ab
Hi
I'm trying to use an unmodified classpath (0.06). I already have
something working with a modified one.
My problem is that the call stack during initialization of the System
class I looks something like
LOG: called: java/lang/System.()V()
LOG: called:
java/lang/System.loadLibrary(Ljava/la
5 matches
Mail list logo
