[COCOON-1876] XMLDBTransformer blows up Saxon

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1.9
• Fix Version/s: 2.1.10, 2.2
• Component/s: Blocks: XML-DB
• Other Info: Patch available
• Assignee: Antonio Gallardo Rivera
• Reporter: Don Grodecki
• Created: 06/Jul/06 03:42
• Updated: 14/Oct/06 02:45
• Resolved: 11/Jul/06 13:00

Description

The XMLDBTransformer blows up Saxon, which does not like null URIs. The
following fix seems to work, replacing null in the first parameter to
addAttribute with "".
                // Report result
                AttributesImpl attrs = new AttributesImpl();
                attrs.addAttribute("", XMLDB_QUERY_OID_ATTRIBUTE,
                        XMLDB_QUERY_OID_ATTRIBUTE, "CDATA", this.key);
                attrs.addAttribute("", XMLDB_QUERY_TYPE_ATTRIBUTE,
                        XMLDB_QUERY_TYPE_ATTRIBUTE, "CDATA", this.operation);
                attrs.addAttribute("", XMLDB_QUERY_RESULT_ATTRIBUTE,
                        XMLDB_QUERY_RESULT_ATTRIBUTE, "CDATA", result);

The API being called is the SAX org.xml.sax.ContentHandler.createElement().
From the Interface definition at http://www.saxproject.org/apidoc/index.html:
"Parameters:
uri - the Namespace URI, or the empty string if the element has no Namespace
URI or if Namespace processing is not being performed
..."

Note that a null value is not specified as one of the options:

Both the versions that I have, which are saxon8 (jar contents dated
4/7/2005) and saxonB-8.7.3 (the latest), blow out with a
NullPointerException.

I have used Saxon quite a bit, for XSLT 2.0, and the only calls to Saxon
with null URIs have been from the XMLDBTransformer.