On Wed, Sep 15, 2010 at 1:27 AM, Stefan Bodewig <bode...@apache.org> wrote: > On 2010-09-14, Rafael de F. Ferreira wrote: > >> From a cursory inspection of org.apache.tools.ant.AntClassLoader, it >> seems Ant only delegates to the system ClassLoader if the class being >> loaded belongs to a fixed set of packages[1]. > > No, Ant almost always delegates to the system classloader first. > AntClassLoader has a parentFirst option that can be used to make it look > into its own classes before delegating when set to false (it is true by > default). The list of packages you've found are the packages that will > always be loaded from the system classloader even if parentFirst is > false. > >> I've run into an issue with ant's classloading strategy. When I try to >> run a Java class with the <java> task, I get a ClassNotFoundException >> for com.sun.xml.internal.ws.spi.ProviderImpl. > > Are you sure the class is available from the system classloader?
Yeah, you're right. The stack trace shows that AntClassLoader tries to load with the parent classloader, catches CNFE and then tries to find it by looking at the path components. I'm actually using Ant's java task from Gradle and it's probably messing up the parent classloader... Thanks for the help. > > Stefan > >> [1] >> http://www.google.com/codesearch/p?hl=en#9iXYxNufh_Y/trunk/src/main/org/apache/tools/ant/util/JavaEnvUtils.java&l=324 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@ant.apache.org > For additional commands, e-mail: user-h...@ant.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@ant.apache.org For additional commands, e-mail: user-h...@ant.apache.org
