Carsten Ziegeler wrote:
But there is another reason for this mail: Now with the current XSLTC we can switch to it as default processor in 2.0 too, can't we?
I'm currently -1 on this because imho xsltc has not proven to be 100% working and I think we should at least in 2.0.x have a fully working xslt processor as default.
Knowing the problems many users have was the reason for my question. I will at least add XSLTC to cocoon.xconf and sitemap to make it easily usable.
Seems OK to me. Not only does XSLTC _still_ have some issues, the Xalan folks are not very active in applying patches, too.
But still, people who want to make use of XSLTC will be happy to see it being made easily usable.
</Steven> -- Steven Noels http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center Read my weblog at http://blogs.cocoondev.org/stevenn/ stevenn at outerthought.org stevenn at apache.org
