You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And this is something that a SAX parser for example will refuse to
process again because of this strange binding of the xml namespace to a
new prefix.
Any ideas why this happens?
Expected behavior
The XSLT servlet should not produce XML with an invalid xm namespace prefix for the reserved http://www.w3.org/XML/1998/namespace namespace URI.
To Reproduce
The following XQSuite demonstrates that directly calling transform:transform produces the expected result, while the same transformation processed by the XSLTServlet produces an unexpected result. Here is the test result:
<testsuitepackage="http://exist-db.org/xquery/test"timestamp="2020-05-15T16:38:07.728-04:00"tests="2"failures="0"errors="1"pending="0"time="PT0.024S">
<testcasename="directly-transform"class="t:directly-transform"/>
<testcasename="pass-through-controller"class="t:pass-through-controller">
<errortype="err:FODC0005"message="Invalid argument to fn:doc or fn:doc-available. exerr:ERROR Error while parsing XML: The prefix "xml" cannot be bound to any namespace other than its usual namespace; neither can the namespace for "xml" be bound to any prefix other than "xml"."
/>
</testcase>
</testsuite>
Describe the bug
As described by @simar0at on exist-open:
Expected behavior
The XSLT servlet should not produce XML with an invalid
xm
namespace prefix for the reservedhttp://www.w3.org/XML/1998/namespace
namespace URI.To Reproduce
The following XQSuite demonstrates that directly calling transform:transform produces the expected result, while the same transformation processed by the XSLTServlet produces an unexpected result. Here is the test result:
The test:
To run this in test, save it to the database as
/db/test.xq
, and trigger the test via this query: eXist-db/eXide#224 (comment).Context (please always complete the following information):
Additional context
conf.xml
? noneThe text was updated successfully, but these errors were encountered: