DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=24220>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=24220

DocumentFragment returned by extension element causes multiple SAX endDocument() events

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
          Component|org.apache.xalan.extensions |org.apache.xml.utils
         Resolution|DUPLICATE                   |
            Summary|DocumentFragment returned by|DocumentFragment returned by
                   |extension element cause     |extension element causes
                   |multiple SAX endDocument()  |multiple SAX endDocument()
                   |events                      |events



------- Additional Comments From [EMAIL PROTECTED]  2004-08-25 20:24 -------
I don't know what triggered Christine Li to believe that this bug is a 
duplicate of 25710. That bug is something totally different IMO.

Anyway I'm reopening this bug as it still persists in the current CVS HEAD and 
it renders Barcode4J's (formerly Krysalis Barcode) Xalan extension virtually 
useless in conjunction with Apache FOP if output from Xalan is piped into FOP 
using SAX.

I've also finally managed to find the time to fix the bug. Since I haven't 
managed, yet, to run all the test suites I can't tell if the patch breaks 
anything. At least it passes the test case I've attached when submitting this 
bug. I will give the test suites another try tomorrow when I'm fully awake 
again.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to