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=24724>. 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=24724 element order matters on keyref checking? ------- Additional Comments From [EMAIL PROTECTED] 2003-11-17 18:11 ------- Actually, I believe it's the same fix. Use the inverse of the if statement for isMatched for the if statement for the first continue in XPathMatcher.startElement. This makes sense with teh comment "try next xpath, if not matching". So I'd assume you'd want to do the same test as isMatched, only for a specific location path. I'll attach a patch shortly. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
