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

Matt Sergeant wrote:
> On Friday, Nov 22, 2002, at 15:21 Europe/London, Robin Berjon wrote:
>> I've been going back and forth on that one, but after my last attempt 
>> (and failure) to patch XSP.pm I've become convinced that XSLT is the 
>> way to go. Starting from there we abandon the idea of ever switching 
>> XSP to SAX, and give the produced code full access to its own DOM :)
> 
> No.no.no.no!

One of these days I'll do it, I won't call it XSP because you'd yell but
I'll do 
it ;) Maybe doing it the RSS way and calling it "XSP 27.0" would work :-p

> This is a really bad idea. You end up with Cocoon. AxKit is fast and 
> light for a reason. XSP.pm isn't *that* hard to fix. Give me a test case 
> and I'll hack on it.

Libxslt is hellishly fast. XSP.pm is not that complicated, but fixing the
last 
namespace bug I encountered may be trivial to some, it certainly looked
hairy to 
me.

The problem was (I don't have test cases handy) that it randomly remapped 
namespace prefixes on output, and got very mixed up when generating
prefixes. 
The basic outcome was quite simply that it made it impossible to use XSP to produce namespaced documents (the workaround being to suppress namespaces).
I 
don't know if it's still there or if it was fixed, this being about a CVS 
version between 1.5 and 1.6. It was introduced by a patch that fixed
another bug 
regarding prefixes.

> This is the first bug reported in XSP.pm for about 
> a year, so there's not much to fix.

*cough* =)

-- 
Robin Berjon <robin.berjon [at] expway.fr>
Research Engineer, Expway
7FC0 6F5F D864 EFB8 08CE  8E74 58E6 D5DB 4889 2488