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=5761>. 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=5761 Multi Level Sorting fails when select-statement returns no result in xsl:sort ------- Additional Comments From [EMAIL PROTECTED] 2002-01-09 07:51 ------- See test sorterr10 for some perspective on this issue, or at least a related one. The issue there is that the lower-level sort is clearly only meaningful inside the upper-level sort. If any one of the levels is completely unusable, we should just proceed in document order. However, if a level is "usable" to the extent that it can be interpreted as all-values-equal (mass tie), then we could sort just as we do when a level is fully usable and its data just happens to be equal for all sorted items. That leads us to the question of whether <xsl:sort select="@NoSuchAttr"/> which could be detected when none of the elements to be sorted has a @NoSuchAttr attribute, indicates a stylesheet problem. I think it does, and I think the person running the stylesheet would want to know about it.
