Nested element constructors cause loss of namespace bindings
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zorba |
Fix Released
|
Medium
|
Federico Cavalieri |
Bug Description
Consider this query:
element {QName("http://
{
element {QName("","b")}
{
"inner"
}
}
In zorba and all other libraries it creates as expected:
<?xml version="1.0" encoding="UTF-8"?>
<bind xmlns="http://
Notice that b contains xmlns=""
Consider this query now:
element {QName("http://
{
element {QName("http://
{
element {QName("","b")}
{
"inner"
}
}
}
This one in zorba creates:
<?xml version="1.0" encoding="UTF-8"?>
<bind xmlns="http://
Notice that b inherits xmlns="http://
I would expect the result that is given by Saxon and BaseX:
<?xml version="1.0" encoding="UTF-8"?>
<bind xmlns="http://
<named:middle xmlns:named="http://
<b xmlns="">inner</b>
</named:middle>
</bind>
Notice that b contains xmlns=""
Changed in zorba: | |
status: | Fix Released → Fix Committed |
milestone: | none → 2.1 |
Changed in zorba: | |
status: | Fix Committed → Fix Released |
fixed in rev. 11986