cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <>
Subject [Vote] Make Xalan the default xslt processor again [was: RE: Releasing 2.1]
Date Fri, 01 Aug 2003 08:16:07 GMT
There are several problems with xsltc which makes Cocoon in some
scenarios unusable. We have several problem reports and I know
from many customers that they all had to disable xsltc and use
xslt in their environment.

It's ok to have xsltc as the default for development cycles to
help the xalan team find bugs, but I think it's not good to
have it as the default for the final release as most users
have to change this default setting anyway.

So, I'm +1 on making xalan the default for the final release again.

What do you think?


Simon Hürlimann wrote:
> Am Donnerstag, 31. Juli 2003 17.46 schrieb Joerg Heinicke:
> > Some issues:
> >
> > 1. POI: No real problem, but what about the code move to the POI
> > project? They seem to prepare the 2.0 release, so I guess they only have
> > no time at the moment ...
> >
> > 2. XSLTC: Geoff already mentioned it. I know of two heavy bugs in our
> > 2.5.1 XSLTC:
> > : stylesheet
> > includes, seems to be already fixed in XSLTC CVS.
> > : top-level
> > variable with document(). This bug is so annoying because the stylesheet
> > "works" in a way, but the cause of the failure is not obvious. And we
> > don't know the reason for it until now: XSLTC command line works, Xalan
> > works. But if we switch from Xalan to XSLTC in Cocoon the stylesheet
> > stops working.
> There's another XSLTC Bug that affects Cocoon. If you use a
> cocoon:/ URL in
> XSLTs document() function, the URI is prepended by the
> stylesheets path. That
> was a realy annoying bug that took me quite some time. The only "fix" for
> this bug is to switch back to Xalan:

View raw message