You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Antonio Gallardo <ag...@agsoftware.dnsalias.com> on 2003/11/07 11:48:35 UTC
[VOTE] Switch default xslt tranformer to xsltc
Hi:
Sometime ago we agreed to use XSLTC as the default XSLT transformer in
Cocoon. But then a bug in xsltc made us to switch back to xalan.
Now the bug is fixed in XSLTC so please vote if you agree to switch again
to XSLTC as the default XSLT tranformer in Cocoon.
Here is my vote:
+1
Best Regards,
Antonio Gallardo
Re: [VOTE] Switch default xslt tranformer to xsltc
Posted by Antonio Gallardo <ag...@agsoftware.dnsalias.com>.
Joerg Heinicke dijo:
> On 07.11.2003 23:25, Antonio Gallardo wrote:
>
>> Joerg Heinicke dijo:
>>
>>>One, I still remember was the usage of document() in a top-level
>>> variable.
>>
>>
>> Can you check if this is still an issue?
>
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20381
>
> still open.
Yep. Can you check it?
Best Regards,
Antonio Gallardo
Re: [VOTE] Switch default xslt tranformer to xsltc
Posted by Joerg Heinicke <jh...@virbus.de>.
On 07.11.2003 23:25, Antonio Gallardo wrote:
> Joerg Heinicke dijo:
>
>>One, I still remember was the usage of document() in a top-level variable.
>
>
> Can you check if this is still an issue?
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20381
still open.
Joerg
Re: [VOTE] Switch default xslt tranformer to xsltc
Posted by Antonio Gallardo <ag...@agsoftware.dnsalias.com>.
Joerg Heinicke dijo:
> One, I still remember was the usage of document() in a top-level variable.
Can you check if this is still an issue?
Best Regards,
Antonio Gallardo
Re: [VOTE] Switch default xslt tranformer to xsltc
Posted by Joerg Heinicke <jh...@virbus.de>.
On 07.11.2003 11:48, Antonio Gallardo wrote:
> Hi:
>
> Sometime ago we agreed to use XSLTC as the default XSLT transformer in
> Cocoon. But then a bug in xsltc made us to switch back to xalan.
>
> Now the bug is fixed in XSLTC so please vote if you agree to switch again
> to XSLTC as the default XSLT tranformer in Cocoon.
-0
I only don't want to switch until we know XSLTC is a real alternative to
Xalan. Some bugs seem to be fixed now. But be sure there were more. One
I still remember was the usage of document() in a top-level variable.
Joerg
Re: [VOTE] Switch default xslt tranformer to xsltc
Posted by Torsten Curdt <tc...@vafer.org>.
Carsten Ziegeler wrote:
> Antonio Gallardo wrote:
>
>>Sometime ago we agreed to use XSLTC as the default XSLT transformer in
>>Cocoon. But then a bug in xsltc made us to switch back to xalan.
>>
>>Now the bug is fixed in XSLTC so please vote if you agree to switch again
>>to XSLTC as the default XSLT tranformer in Cocoon.
>>
>>Here is my vote:
>>
>>+1
>>
>
> +0
>
> I prefer waiting until the release is out - we haven't tested it yet, so
> perhaps it's better to wait for the 2.1.4 release.
even -0.5
...last time we switched right before a release and IIRC
it was not the best choice
Let's test it first!
--
Torsten
Re: [VOTE] Switch default xslt tranformer to xsltc
Posted by Bertrand Delacretaz <bd...@apache.org>.
Le Vendredi, 7 nov 2003, à 15:18 Europe/Zurich, Carsten Ziegeler a
écrit :
> Antonio Gallardo wrote:
>>
>> Sometime ago we agreed to use XSLTC as the default XSLT transformer in
>> Cocoon. But then a bug in xsltc made us to switch back to xalan.
>>
>> Now the bug is fixed in XSLTC so please vote if you agree to switch
>> again
>> to XSLTC as the default XSLT tranformer in Cocoon.
+0
I'm with Carsten, there might be subtle effects to this, better wait
for after the release.
-Bertrand
RE: [VOTE] Switch default xslt tranformer to xsltc
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Antonio Gallardo wrote:
>
> Sometime ago we agreed to use XSLTC as the default XSLT transformer in
> Cocoon. But then a bug in xsltc made us to switch back to xalan.
>
> Now the bug is fixed in XSLTC so please vote if you agree to switch again
> to XSLTC as the default XSLT tranformer in Cocoon.
>
> Here is my vote:
>
> +1
>
+0
I prefer waiting until the release is out - we haven't tested it yet, so
perhaps it's better to wait for the 2.1.4 release.
Carsten