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=6833>. 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=6833 ArrayIndexOutOfBoundsException ------- Additional Comments From [EMAIL PROTECTED] 2002-03-21 14:47 ------- We seem to be experiencing the same problem. Upgrading to 2.3.1 made everything much faster, but some of the elements disappeared from the output. Investigation turned out that xalan must have gotten very confused about its internal datastructures somewhere in the process. Depending on how we tried to trace the processing an ArrayIndexOutOfBoundsException would occur. It seems that a nodeset returned by xalan:nodeset can somehow be broken if a lot of other processing has been going on. The Xalan-C processor and saxon does give the correct/expected output. So did the 2.2.x versions of xalan-j. Any solution whould be most welcome
