cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steven Noels <>
Subject Re: [FYI] Profiling Cocoon...
Date Sun, 06 Oct 2002 21:28:31 GMT
>> 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?

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.

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.

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 

Steven Noels                  
Outerthought - Open Source, Java & XML Competence Support Center            

To unsubscribe, e-mail:
For additional commands, email:

View raw message