Sorry for the delayed response, my PC power supply burnt.
Would it be too painful to do what Jeremy is when XSLTC is broken? I though we all felt that long term we want XSLTC as the main Cocoon processor. Making XSLTC default now in 2.1-dev is the only reasonably fast way to have it working for the next major release. Otherwise it's just taking way too long for individuals to test it while the XSLTC team is pretty fast at resolving issues. I think we should take advantage of their current availability. Having a 5x faster processor is just too tempting to miss. If you think I'm wrong, vote against, otherwise vote for keeping XSLTC as default for now. +1 Gianugo, Tom, can you please communicate the problems to the XSLTC team? Also, for those who encounter new bugs, in order to reduce turn around time, please send bugs with sypmtoms directly to Tom and the xsltc-team list in addition to cocoo-dev. Thanks. Ivelin On Monday, July 1, 2002, at 01:08 PM, Carsten Ziegeler wrote: > Hi, > > with the latest switch to XSLTC, Cocoon isn't working anymore for > me. My system is JDK 1.4.0.01, W2K, Tomcat 3.3a. JDK 1.3.1, MacOSX 10.1.5, TomCat 4.0.4-b3 I don't get exceptions, but I get some expressions not returning results with xsltc where they do with xalan. (I'll do a proper examination of what's going wrong later). Switching my sitemap's default transformer to 'xalan' solves all the problems. regards Jeremy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
