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=13579>. 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=13579 Performance problem with Xalan 2.0 -> 2.4 ------- Additional Comments From [EMAIL PROTECTED] 2002-10-15 19:51 ------- Yes, DOM2DTM is built by walking the DOM tree in document order. That's the way it was architected, so this is working as designed. Yes, we realize it's suboptimal, but at the time we did the DTM cutover SAX was our primary usage mode. You may want to experiment with the DOM2DTM2 implementation in the XSLT20 branch of the CVS tree -- there's a static final boolean in DTMManagerDefault which has to be set true to enable it -- which does build the model nonlinearly. However, it is not yet performance tuned, and there are some definite challenges in this approach, so it may not yet be a net win. But it's our current best attempt to reach in the direction you've suggested. Given that the correct results are produced (if not as quickly as desired), and given that we do have DOM2DTM2 in process as an experimental attempt to address this, I'd suggest downgrading the severity to Enhancement, and setting an appropriate Priority to reflect how urgently you feel this Enhancement is required.
