[XALANJ-1706] [PATCH] DocumentFragment returned by extension element causes multiple SAX endDocument() events

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.7
• Fix Version/s: 2.7.1
• Component/s: Other
• Environment: Operating System: All; Platform: All
• Bugzilla Id: 24220
• Assignee: Brian Minchau
• Reporter: Jeremias Maerki
• Created: 29/Oct/03 23:01
• Updated: 12/Dec/07 07:14
• Resolved: 22/Oct/05 11:48

Description

At Krysalis Barcode (http://www.krysalis.org/barcode) I have a Xalan extension
which creates barcodes in SVG format [1]. Until recently I've used an
extension function for that. As I was able to create an extension element for
SAXON I wanted to do the same for the Xalan-extension. But here's the problem:

The extension element (like the extension function where it works correctly)
returns a DocumentFragment containing the generated barcode in SVG format. In
the case of the extension element the DocumentFragment is processed by a
TreeWalker which issues start/endDocument() SAX events although it shouldn't
IMO. This behaviour causes Apache FOP to crash with an NPE because more than
one endDocument() SAX event is sent to FOP by Xalan.

I will attach a test case for the bugzilla test directory. Current CVS (HEAD)
and 2.5.1 fail in this test. I will try to find a bugfix but if someone more
intimate with the code beats me to it, so much better.

[1] http://cvs.sourceforge.net/viewcvs.py/krysalis/krysalis-
barcode/src/java/org/krysalis/barcode/xalan/BarcodeExt.java