Thanks for your quick answer.
Just a precision : you can reproduce the problem by calling replaceNode2() directly without calling neither insertNode() nor replaceNode() before. The problem occurs when the replace command does not declare the new namespace at the top level node.
Regards,
Laurent
De : Lukas Kircher [mailto:lukaskircher1@googlemail.com]
Envoyé : mercredi 2 novembre 2011 17:26
À : Laurent Chevalier
Cc : basex-talk@mailman.uni-konstanz.de
Objet : Re: [basex-talk] 'replace node' with new XML namespace prefix
Hi Laurent,
we are currently revising our internal namespace structures and are quite positive that this issue will be resolved in the process. For now we are a bit hesitant to include further fixes that might blow up the code unnecessarily and cost us precious time better spent on the revision of the module itself.
Thanks for the detailed test - we will include this into the testing process. I also opened a GitHub issue as a reminder [1].
Sorry for the inconveniences - regards,
Lukas