You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Carsten Ziegeler <cz...@s-und-n.de> on 2003/08/01 10:16:07 UTC
[Vote] Make Xalan the default xslt processor again [was: RE: Releasing 2.1]
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?
Carsten
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:
> > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20308 : stylesheet
> > includes, seems to be already fixed in XSLTC CVS.
> > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20381 : 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:
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21857
Re: [Vote] Make Xalan the default xslt processor again [was: RE:
Releasing 2.1]
Posted by Geoff Howard <co...@leverageweb.com>.
Carsten Ziegeler wrote:
> So, I'm +1 on making xalan the default for the final release again.
>
> What do you think?
+1
Geoff
Re: [Vote] Make Xalan the default xslt processor again [was: RE: Releasing 2.1]
Posted by Bertrand Delacretaz <bd...@codeconsult.ch>.
>> So, I'm +1 on making xalan the default for the final release again.
+1
-Bertrand
Re: [Vote] Make Xalan the default xslt processor again [was: RE: Releasing 2.1]
Posted by Jeff Turner <je...@apache.org>.
On Fri, Aug 01, 2003 at 10:16:07AM +0200, Carsten Ziegeler wrote:
> 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.
+1
--Jeff
> What do you think?
>
> Carsten
>
Re: [Vote] Make Xalan the default xslt processor again [was: RE:
Releasing 2.1]
Posted by Gianugo Rabellino <gi...@apache.org>.
Carsten Ziegeler wrote:
> So, I'm +1 on making xalan the default for the final release again.
>
> What do you think?
+1
--
Gianugo Rabellino
Pro-netics s.r.l. - http://www.pro-netics.com
Orixo, the XML business alliance - http://www.orixo.com
(Now blogging at: http://blogs.cocoondev.org/gianugo/)
Re: [Vote] Make Xalan the default xslt processor again [was: RE: Releasing 2.1]
Posted by Stefano Mazzocchi <st...@apache.org>.
On Friday, Aug 1, 2003, at 10:16 Europe/Rome, Carsten Ziegeler wrote:
> 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?
+1
--
Stefano.
RE: [Vote] Make Xalan the default xslt processor again [was: RE: Releasing 2.1]
Posted by Reinhard Pötz <re...@gmx.net>.
From: Carsten Ziegeler
> 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
+1 too for the release (XSLTC is hell if you use namespaces)
then we should set XSLTC as default xslt processor again.
Cheers,
Reinhard