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

Aye, I hear you. I think it wouldn't be horrendously hard to do though. I
mean 
creating the scaffold of the page isn't too bad, and then its just a matter of outputting the same code XSP generates now every time it encounters 
content in the page. I bet if 4 or 5 of us attacked it we could get it to 
work in a few weeks. The only question would be taglib compatibility, I'm 
betting that existing taglibs would need some patches, mostly to 
TaglibHelper/SimpleTaglib. 

I never really honestly thought much of the SAX approach. In THEORY its
nice, 
but once I sat down and considered the logic required to do it, it got
scary 
fast! It would have to be a pretty elaborate stack-based state-machine. 

On Friday 22 November 2002 10:21 am, Robin Berjon wrote:
> Tod Harter wrote:
> > It seems to me that XSP itself is an example of an application that
> > should be written in XSLT....
>
> 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 :)
>
> Aah, if I had the time I'd implement that ;-)

-- 
Tod G. Harter
Giant Electronic Brain