ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Magesh Umasankar" <>
Subject Re: ExecuteJava and initializeClass
Date Thu, 17 Jan 2002 02:55:39 GMT
From: "Conor MacNeill" <>

> >
> > > You'll need a valid Constructor object for that and I'm not sure
> > > it will work but worth a try.
> >
> > JVM guarantees that each class *will* have a constructor, either
> > provided by default or explicitly specified.  So, getting a constructor
> > object is easy and it can be safely assumed that we will get
> > a constructor object when using reflection.
> Yes, I know that :-). 

D'oh! I understood your comment wrongly and started off on what little
Java I know ;-)

> What I meant to question is whether when you then call
> that with a set of illegal arguments, will it run the static initializers
> under JDK 1.1. I thought the validation in the reflection code may have
> thrown out first. If you have checked that and it works, cool.

Please look under the evaluation section of

I have checked that after installing my patch, the PRs that you had pointed
to still stay resolved under 1.1.7A, 1.2.1, 1.3.1 while at the same time
doing away with calling no-arg constructor twice.
I am downloading 1.1.8 now to check that out...  Anyway, I am doing
all these tests using Sun JVMs on Windows only.  It would be
helpful if somebody can cross verify this on other platforms as well.
Test to carry out is essentially well defined in
Any volunteers?

> > After you confirm, perhaps, I may even move this piece
> > into AntClassLoader itself.
> Yes, that is where it should be.

That is where it will go, finally, then :-)

> Conor


To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message