2009/08/18 - Apache AxKit has been retired.

> Just downgrade your XML::LibXML to 1.52 until Christian fixes this bug 
> in XML::LibXML. Thanks.

The workaround for this particular bug is fairly simple, and can be done 
on AxKit side, see attatched patch (a simple grep indicated that XSP.pm 
is the only module that uses these constants, so hopefully this fixes 
everything)

However, after fixing this problem I encountered another big problem 
with XML::LibXML::Common::encodeToUTF8. Something is seriously wrong 
when AxKit tries to encode the text nodes of an XSP file...

I haven't done any extended tests, but it seemed like it was somehow 
failing to convert a newline character... (that's what $node->getData() 
returned. It beats me why iconv reported and error indicating that there 
were 4 bytes in that sequence, though)

Anyway *THAT* made me downgrade to XML::LibXML 1.52. I suppose I could 
have avoided it by cut n' pasting the code for encodeToUTF8 from 
XML::LibXML 1.52 to XML::LibXML::Common, but that was too much :)

--d

Index: lib/Apache/AxKit/Language/XSP.pm
===================================================================
RCS file: /home/cvspublic/xml-axkit/lib/Apache/AxKit/Language/XSP.pm,v
retrieving revision 1.22
diff -u -r1.22 XSP.pm
--- lib/Apache/AxKit/Language/XSP.pm	10 Sep 2002 16:27:30 -0000     
1.22
+++ lib/Apache/AxKit/Language/XSP.pm	11 Oct 2002 05:03:54 -0000
@@ -930,6 +930,13 @@
 package AxKit::XSP::SAXParser;

 use XML::LibXML 1.30;
+BEGIN
+{
+    if($XML::LibXML::VERSION >= 1.53) {
+	 require XML::LibXML::Common;
+	 XML::LibXML::Common->import( qw/ :libxml :encoding / );
+    }
+}

 sub new {
     my ($type, %self) = @_;