I can run the transformation using the sample
Web App provided with the Xalan 2.7.0 package. And it formats right. I am
using the JAXP API’s inside a Servlet. The way it is setup is that a
templates object is created, and then that object creates a new transformer and
transforms the output into a StringWriter. I am trying to verify my classpath
for my webapp right now…but I am stuck on where else to look.
From: Christine Li
[mailto:jycli@xxxxxxxxxx]
Sent: Wednesday, November 09, 2005
12:02 PM
To: xalan-j-users@xxxxxxxxxxxxxx
Subject: RE: XSL for-each problem
>I just looked. I
made sure that serializer.jar, xalan.jar, xml-apis.jar, xercesImpl.jar are
included in the classpath. Also, I am using Tomcat 5.5.12 and JDK
1.5.0_05.
>Is there any other dependencies that I should be aware
of? Christine, how did you run the files that I sent you to produce the
output below?
I
used the command line process, org.apache.xalan.xslt.Process. I thought that
Sun JDK 1.5.0 renamed the package name of Xalan classes. Did you use JAXP
APIs inside a Servlet or JSP? Can you try with a stand alone java program to do
the transformation?
Christine
Li
XSLT Development
IBM Toronto Lab
Tel: (905)413-2601
Email: jycli@xxxxxxxxxx
|
|
Try Searching:
servers, voip, java, networking, microsoft ...
|
|
|
| 
