You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@xalan.apache.org by bu...@apache.org on 2002/02/21 22:56:29 UTC

DO NOT REPLY [Bug 6625] - No Locator available to ContentHandler (SAXResult)

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=6625>.
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=6625

No Locator available to ContentHandler (SAXResult)

keshlam@us.ibm.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|Normal                      |Enhancement



------- Additional Comments From keshlam@us.ibm.com  2002-02-21 21:56 -------
SAX locators were designed for use with parsers, where there's a single source 
document. It isn't at all clear whether an XSLT processor, which is convolving 
two or more documents together, should be reporting the location in the XSLT 
stylesheet, the source document(s), or something else entirely. (What if the 
value is computed from the content of several elements and attributes?)

However, I believe it is possible to find out what portion of a stylesheet is 
currently executing by registering a TraceListener. Would that address your 
needs?

(In any case this is a request for Enhancement, not a bug per se, and I've 
changed the severity to reflect that.)