Steven Noels wrote: >>> Discovery #3: >>> >>> use XSLTC as much as possible! >>> >>> NOTE: our current root sitemap.xmap indicates that XSLTC is default >>> XSLT engine for Cocoon 2.1, but the fact is that the XSLTC factory is >>> commented out, resulting in running Xalan. We should either remove >>> that comment or uncomment the XSLTC factory. >>> >>> I vote for making XSLTC default even if this generates a few bug >>> reports. >> >> >> >> >> +1 > > > Do we have an active development community around XSLTC?
We don't, but Xalan does. > Serverside XSLT processing is one of the key usage areas of Cocoon. I > might be wrong on this, but making XSLTC the default, while it is still > known as an incomplete XSLT 1.0 implementation, without the conformance > tests ran ourselves that might prove the contrary, might as well be bad > advertising for Cocoon. My proposal is to turn it on on Cocoon 2.1 as it is in CVS HEAD and maybe when we reach the first beta. Then see what happens. > While the previous problems have been solved, it took some time and > deliberation. Xalan2 is stable. The problem also might be that people > are often misusing XSLT for things that could better be solved with > plain Cocoon components. Correct, but this is not a good reason to have them run their well-thought stylesheets slower, don't you think? > I'm not saying we shouldn't be bugtesting for XSLTC, it's just that I > don't know if the XSLTC community will be there to follow up on our bug > reports. I hear you. Consider it a stress-test of both the software *and* the community around it. Anyway, just a reminder: you never get people to scratch if you don't create some itches :) And if this thing doesn't work out as expected, we can always ship Cocoon 2.1 final with Xalan enabled. What do you think? -- Stefano Mazzocchi <[EMAIL PROTECTED]> -------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
