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=6156>. 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=6156 NullPointerException in org.apache.xpath.objects.XRTreeFrag.xstr ------- Additional Comments From [EMAIL PROTECTED] 2002-01-31 22:26 ------- Mumble mumble mumble - trying to figure out the actual problems here... OK: .jars and CLASSPATHS: You should always use the Xerces parser that comes inside the Xalan distro unless you have a very specific need to use a different parser. The preferred classpath for Xalan-J 2.2 is xalan.jar;xml-apis.jar;xerces.jar (because that included Xerces-J 1.4.4). The preferred classpath for Xalan-J 2.3.D1 and beyond is xalan.jar;xml-apis.jar;xercesImpl.jar (because that included Xerces-J 2.0beta-something). You never need xmlParserAPIs.jar because all needed classes from that are already present in our xml-apis.jar. You never need xml-stds.jar because Joe was just mistyping xml-apis.jar (I think...). OK: potential parser issues: You should be able to use a current Xalan build against either Xerces 1.4.4 or against Xerces 2.0.0beta4 or later. However we may not have tested switching the 'live' parser version after the Xalan code is compiled - I'm not sure exactly how the Xalan build process and Joeseph's Xerces parser interfaces' reflection code interact when we're compiled against one version and then run against the other one. OK: bugfixes: I'm wondering if Myriam's fixes are actually in 2.3D1 or if they're after that. Oh, wait, they should be in TransformerImpl.java r1.118 which does appear to be in 2.3D1 (at least they're tagged that way). We'll need to get a fully reproduceable test case to address this, since it sounds like it may still be a bug.
