ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rainer Noack" <>
Subject RE: classloader and delegating classloader problem
Date Tue, 22 Aug 2006 19:52:15 GMT
Should work, but these issues typically require manipulation of the System
Classloader (resp. User-Classloader).
In Ant, this is the Launcher's Classloader whereas oata.Main, oata.Project
and the rest are loaded via a  System Classloader's childloader. As
discussed in this list some years ago, it may produce curious results if a
class is added to a parent-loader after it is used/load by a childloader.
Handle with care!!!
One can use <classloaderreport/> to debug classloader related issues.



> -----Original Message-----
> From: Antoine Levy-Lambert [] 
> Sent: Tuesday, August 22, 2006 3:59 PM
> To:
> Subject: classloader and delegating classloader problem
> Hello Peter and other,
> does this <classloader/> task address the delegating class 
> loader issue ?
> I am really not knowledgeable about classloaders myself, but 
> remember that I was not able to make a custom task based on 
> JNDI APIs work if the concrete JNDI driver to use (in this 
> case it was a JNDI driver for MQ Series) was not put on the 
> classpath before starting ant. I guess that the explanation 
> in this case is that my custom task invokes the standard JNDI 
> APIs (Context class) which is implemented in the Java 
> runtime, and that this one cannot find the classloader which 
> loaded my task anymore, so does not know about the JNDI driver.
> Would be cool if <classloader/> solves the problem.
> Regards,
> Antoine
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

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

View raw message