DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20256>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20256
SAXImpl$SingletonNodeIDIterator class not found
Summary: SAXImpl$SingletonNodeIDIterator class not found
Product: XalanJ2
Version: 2.5
Platform: PC
OS/Version: Linux
Status: NEW
Severity: Normal
Priority: Other
Component: Xalan-Xsltc
AssignedTo: xalan-dev@xxxxxxxxxxxxxx
ReportedBy: rick@xxxxxxxxxxxxx
CC: r-knowles@xxxxxxxxxxxxxx
In the 2.5 version of Xalan-XSLTC, a normal compile and run seems to work well
(I should say wonderfully well - no bugs and great performance) when executed
with standard interpretive JVMs.
Recently I've been trying to build Xalan-XSLTC with gcj - the end goal being to
make a completely native OS binary tomcat installation, right down to the
servlets and the translets. I've found a bug that only seems to show up there.
There's a reference on line 186 of
org/apache/xalan/xsltc/compiler/util/MethodGenerator.java:
index =
cpg.addInterfaceMethodref("org.apache.xalan.xsltc.dom.SAXImpl$SingletonNodeIDIterator",
NEXTID, NEXT_SIG);
This causes runtime errors on the gcj binary, because the class requested
doesn't exist. The JDK 1.4.1 execution causes no such errors, since it seems
this class is not even called in that case.
Also of interest, this behaviour seems consistent regardless of gcc optimisation
level as well. Maybe a compiler bug, but the fact that the code references a
class that doesn't exist is weird.
I've changed it in my copy to point to
org.apache.xalan.xsltc.dom.SingletonIterator, and it seems to work ok for now.
Any thoughts ? Obviously not high priority, but it looks like some code that has
been refactored and a reference has been forgotten.
Compile details: gcj 3.3 on kernel 2.4.20, glibc 2.3.2, using crimson 1.1.3 and
xalan 2.5.
Hope this helps,
Rick Knowles
|
