Tom,
We don't have enough time to update the document for the Process command
line before the 2.4.1 release. We will do it for the next release.
The problem reported in bug 14148 is that the Process command line cannot
find the translet when it exists. In this case it will try to do the
transformation from the xsl, you will not see any failure. Please use the
following steps to reproduce the problem:
> java org.apache.xalan.xslt.Process -in cars-2.xml -xsl cars-2.xsl -xsltc
-xt -xx
A translet in the name cars_2.class should be generated.
Then run the same command again. The expected behavior is that you should
see a debug message "Transform using translet cars_2". You will not see
this message for the current code because the Process command line cannot
find the translet. It will use the cars-2.xsl to transform and generated
the cars_2.class again. This is not the correct behavior because the -xt
option is supposed to use the translet for transformation. Maybe I can also
put this information into the bug report.
Regards,
Morris Kwan
XSLT Development
IBM Toronto Lab
Tel: (905)413-3729
Email: [EMAIL PROTECTED]
Tom Amiro
<[EMAIL PROTECTED] To: "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]>
M> cc:
Sent by: Subject: problems with new -XSLTC
option
[EMAIL PROTECTED]
11/01/2002 11:38
AM
Please respond to
xalan-dev
Hi,
I just looked at the site doc for 2.4.1 on the
commandline options and don't see the -xsltc
option
http://xml.apache.org/xalan-j/commandline.html
Shouldn't it be documented?
On a related issue, the following bug on the -XSLTC option
has an attached patch, and is in the NEW state, but the
fix already seems to be there is the current code
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14148
Or, at least, I couldn't reproduce the problem using cars-2.xml and
cars-2.xsl
as the names of the files for a test case.
Interesting. In one case something that should be
there isn't and something that wouldn't appear to
be there is.
--
Tom Amiro -- SQE Engineer
WTS - Interoperability and Quality
voice: 781-442-0589 Fax: 781-442-1437
eMail: [email protected]
