[ http://issues.apache.org/jira/browse/XALANJ-1243?page=comments#action_12459661 ] Henry Zongaro commented on XALANJ-1243: ---------------------------------------
I just happened to notice that all four of these issues (XALANJ-1243, XALANJ-1880, XALANJ-1991 and XALANJ-2001) appear to be related to one another because they all seem to describe the same problem with XString.equals, but I haven't investigated further to be certain of that, so I just thought I'd provide that information. XALANJ-2001 contains a patch that avoids the problem, but I didn't like the patch at the same, so it's never been applied. > java.lang.StackOverflowError in XString.equals() > ------------------------------------------------ > > Key: XALANJ-1243 > URL: http://issues.apache.org/jira/browse/XALANJ-1243 > Project: XalanJ2 > Issue Type: Bug > Components: XPath > Affects Versions: 2.4Dx > Environment: Operating System: Solaris > Platform: Sun > Reporter: Wolfram > Assigned To: Xalan Developers Mailing List > Attachments: 1.xml, 1.xsl, xalan-stack-overflow.zip > > > In some special cases I get a StackOverflowError in method equals(XMLString), > line #444 [ if (!obj2.hasString()) return obj2.equals(this); ] > I think this can occur if to XStringForChars-objects are compared, and both > objects haven't been used before. Than the hasString()-method of > XStringForChars returns false for both, resulting in an endless loop. > I patched XStringForChars method hasString() to return always true, > which works for me. > Don't know if this is the right way to solve this bug. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
