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

On Saturday, Nov 23, 2002, at 14:48 Europe/London, Tod Harter wrote:

> What would be so bad about using XSLT to generate perl. Then you can 
> bring the
> full weight of XML processing technology to bear on the configuration 
> of your
> pipelines, which can only be a good thing. Granted it might be a lot 
> less
> efficient at compiling your XSP pages, but the fact is thats fairly
> irrelevant to performance since it only happens once. In a production
> environment you can always spider your site after you make changes in 
> order
> to make sure everything is recompiled before you go live anyhow.

It's not bad per-se. It's just a bad idea to try and rip out our 
excellent implementation of XSP (arguably better designed than Cocoons 
- even most of the Cocoon developers agree with me on this) and replace 
it with something unknown, and in the meantime break both SimpleTaglib 
and TaglibHelper, which only work *because* of our current design.

> In terms of difficulty of management of the system, etc. Its always 
> been my
> opinion that if you can reduce your system to the most common elements 
> and
> processes, and then build good tools to do those tasks that in the 
> long run
> you have the best system, so I'm not convinced that tools like SILLY 
> are such
> bad ideas, they simply need to be presented as one set of 
> possibilities.

We don't need Cocoon's SiLLy - we have at least 3 better alternatives. 
The people involved with Cocoon recognise this. You should too.

It's one bug. Can we fix it and move on? Someone send me a trivial test 
case and I'll hack on it.

Matt.