I haven't worked with Tomcat for quite a while. But I have used Tomcat few years back, so can give some untested advice.
You need to remove all old Xalan and Xerces binaries from Tomcat install folder (I hope you can locate where these binaries lie). Then copy all latest Xalan and Xerces Jars into Tomcat installation. Then after restarting Tomcat, you should be able to use all features in latest Xalan binaries. On Sat, Aug 30, 2008 at 2:30 PM, Nuno Viana (Gmail) <[EMAIL PROTECTED]> wrote: > Dear all, > > I can't seem to find the cause for the problem that I am having. I > have implemented a simple Java method which allows me to apply a XSLT > transformation to an input XML file, thus resulting in an output XML > file as well. > > I am using JAXP (included in JDK5), Xerces 2.9.1 and Xalan 2.7.1 (as > my XSL uses some Xalan extensions such as "tokenize" and "nodeset") to > compile my stylesheet and apply transformation to my input XML doc. > > The problem that I am having is that, after compiling my java sources > into a Jar, and running the main() from the command-line (from inside > the WEB/lib for my WebApplication) - It Works FINE!!! However, when I > call it from a JSP file (under Tomcat 5.5), it reports an error saying > that there it could not compile the XSLT, as he could not find a > "1-argument method for the xalan:tokenize()" function. > > I though it was a problem related with the possible XML parser > implementation that ships with tomcat, so I tried adding the > xerces-Impl.jar, xalan.jar, xml-apis.jar, serializer.jar JAR files to > the Tomcat "endorsed" library (as running from the command-line and > from within the JSP file, printed a diferent Xalan version). > > However doing this didn't solve the problem... > > Has anyone experienced problems in trying to compile XSLT stylesheets > using Xalan extensions under a JDK5 / Tomcat 5.5 configuration (while > still working via a command-line)? > > > PS: > I have already tried successfully doing an "exec" which calls a > "xslt.sh" script and sets the appropriate paths to solve the problem, > but I wouldn't like to continue using it, as it is a bit "dumm" to > execute a Java program using "exec", from within a Java runtime > environment (not to mention the memory allocation costs that this > solution has) > > Any help/shared experiences on this subject would be greatly appreciated!!! > > Many thanks, > > Gizmo ([EMAIL PROTECTED]) -- Regards, Mukul Gandhi
