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) ------- Additional Comments From [EMAIL PROTECTED] 2002-02-21 22:14 ------- Hi Joe, What you say about the Locater makes sense. I am already using TraceEvents for something else. One could register a listener for GenerateEvent's. But those are fired at the same time as the events on the handler. I.e. startElement() is fired from flushElem() and so the transformer object has the same problem I mentioned before. To inform this discussion, I am one of the people working on Stylus Studio. I am now implementing native support for debugging using Xalan. So in a future release you'd be able to use our debugging environment to drive the xalan processor (running in-process with Stylus). That's why I need to know the current point in the XSL stylesheet when I get an output sax event. (next time, I will be sure to file requests like this as enhancements, not bugs).
