I ran into the same problem using iAS/iPlanet. But some of the extension functions depend on other classes that I cannot add to lib/ext. They have to be only in the classes WEB-INF. Matt, Do you have a solution from iPlanet yet? Thanks Uma -----Original Message----- From: Gary L Peskin [mailto:[EMAIL PROTECTED]] Sent: Friday, May 04, 2001 3:26 PM To: [EMAIL PROTECTED] Subject: Re: extension functions in Xalan-Java 2.0.1 (using TraX/JAXP) Matt -- I'm glad that it worked out. It seems that there must be some way to tell iPlanet what classpath to use. XalanJ2 should be using the context class loader, if that is helpful info for iPlanet support. If you can't get an answer from them, come back here. There must be other iPlanet users using extension functions who have solved this problem. Gary Matt Coarr wrote: > > Great news (sort of)! It is not a problem with xalan or my code, but rather a problem with the classloader/classpath. When i jared up my extension function and put it the jre's lib/ext directory, the extension function was sucessfully called and the correct results are generated!! I'll take the classpath problem up with iPlanet tech support. > > Thanks for all the help! It provided some very useful information. > > Matt > > Matt Coarr wrote: > > > My extension function is implemented by org.mitre.isis.ClassAds.XmlHandler. The class file is packaged in my war file as WEB-INF/classes/org/mitre/ClassAds/XmlHandler.class and > > deployed to c:\iplanet\ias6\ias\APPS\classads\classads\WEB-INF\classes\org\mitre\isis\Cl assAds\XmlHandler.class. I guess the next logical step would be to package this in a jar file > > and try something like putting this jar file in the extension directory.
