Re: [gdome]test-document fails with libxml2 2.4.24 (and 2.4.23)

["T.J. Mather" <tjmather tjmather com>]

I was able to fix the test failures by adding

  <!ATTLIST tns:NODE
    ITEM ID #REQUIRED
  >

for tns:NODE as well as NODE.

It seems that in libxml2 2.4.23 and greater, you are required to prefix
the node with the namespace in the DTD def, which I believe is the correct
behavior...

Also, I fixed a problem with test-xpath.c where in libxml2 2.4.23 and
greater, the //namespace::* query now returns the namespaces in a
different order (xml namespace first, then xmlns:a), by changing the test 
to expect the results in that order.  I'm not sure about this, as I 
looked at the XPath spec and couldn't find anything about the order of the 
namespace axis.

So now the tests pass for libxml2 2.4.23 and greater.  Unfortunately, the
test-xpath test may fail for 2.4.22 and lower.  I checked these changes
into CVS, please let me know if I should change anything.

Regards,
TJ

On Sat, 31 Aug 2002, T.J. Mather wrote:

> I tested this on Mandrake 9.0beta3 and Redhat 7.2, libxml2 2.4.23,
> and libxml2 2.4.24 (it works fine for libxml2 2.4.22 and under).
> 
> Here the output of the test-document test:
> 
> # ./test-document
> ...........test_document1
> ...test_document2
> 
> Document.getElementById("1"), NULL
> Document.getElementById("3"), NULL
> Document.getElementById("5"), NULL
> Document.getElementById("7"), NULL.
> Document.getElementByTagName("urn:test.tst","NODE"), wrong 0-th item
> Document.getElementByTagName("urn:test.tst","NODE"), wrong 1-th item
> Document.getElementByTagName("urn:test.tst","NODE"), wrong 2-th item
> Document.getElementByTagName("urn:test.tst","NODE"), wrong 3-th item.
> ** CRITICAL **: file gdome-xml-node.c: line 1343 
> (gdome_xml_n_removeChild): assertion `old_priv != NULL' failed.
> 
> NODELIST IS NOT LIVE!!.test_document3
> 
> I'm going to take a look at this and see if I can find the problem.
> 
> -TJ