You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@xalan.apache.org by bu...@apache.org on 2003/07/31 21:21:38 UTC

DO NOT REPLY [Bug 22029] New: - Bug 13851 now in J2SE 1.4.2

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=22029>.
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=22029

Bug 13851 now in J2SE 1.4.2

           Summary: Bug 13851 now in J2SE 1.4.2
           Product: XalanJ2
           Version: 2.0.0
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: org.apache.xpath
        AssignedTo: xalan-dev@xml.apache.org
        ReportedBy: aveyc@hmc.harvard.edu


Sun's new release of Java 2 Std Edition 1.4.2 now bundles (in rt.jar) a version 
of org.apache.xpath.object.XString that still exhibits the behavior reported in 
Bug #13851 (Stack overflow). Placing this class in rt.jar makes it very hard to 
work around, except by using -Xbootclasspath/p.