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=10643>. 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=10643 xalan hangs indefinitly consuming 100% CPU ------- Additional Comments From [EMAIL PROTECTED] 2002-07-10 15:28 ------- Problem confirmed, though I'm testing with a slightly divergent version of Xalan, so this may not be valid. Very preliminary analysis: You're never returning from the add-next-activities template... which you _haven't_ salted with messages, as you did some other parts of your stylesheet. You're entering the Otherwise clause of that template. The problem seems to be in computation of toTrans. A bit of experimentation suggests that the glitch is occuring in the predicate, since I can retrieve the @From successfully. Odd result: If I print out the value of that same XPath as a message, *EXCEPT* for the /@Id portion of the predecate, immediately before computing toTrans, the stylesheet runs to completion. If I try to print out the full XPath with the /@ID, it freezes after the message is displayed but before toTrans is done computing. Unfortunately the failure is _not_ occurring under my preferred debugger, so I can't easily see exactly where it's stopping.
