I had a problem with a custom task which I had written which was using JNDI. This task had a runtime dependency on a JNDI driver for MQ Series. Adding the JNDI driver to the classpath of the taskdef never worked, the only thing that worked was to start ant with a -lib fullpathtoMQJNDI.jar. I assumed that the reason is that the JNDI driver is loaded by the JDK runtime, so only indirectly from my custom task.
JDK code, loaded by the bootstrap class loader, depends I believe on the context class loader to locate/load discovered services. I believe the CL set by Launcher is set as the context loader, which is why it worked, whereas the CL you created in your custom task wasn't the context one maybe? I'm just guessing of course. --DD --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
