Re: argument type mismatch when using fn:replace
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thomas, On 8/4/2010 5:09 PM, Thomas Ernest wrote: I remember having this problem, when I used the same version of Cocoon one year ago. I'm not 100% sure, but I mean fn:replace is a function belonging to XPath 2.0 [1] and Cocoon 2.1.11 integrates a Xalan implementing XPath 1.0 only. That would certainly explain the problem. My Cocoon has Xalan-2.7.1, which only supports XSLT 1.0 and XPath 1.0. It's odd that Xalan 2.7.1 is the latest version available. Is Xalan dead? Does Saxon replace it? You should check which version of Xalan do you use and be sure this version implements XPath 1.0 only. You were right, although I was thrown by the fact that changing the stylesheet version to 2.0 allowed me to use the xsl:analyze-string element, which is apparently not implemented. I guess anything not implemented is ignored. Does that sound right? For the time being, I implemented a manual search-and-replace which does work with Cocoon 2.1.11. I think my best option is to upgrade Cocoon. It's about time, anyway. It's always so nerve-wracking to upgrade something so vital to your product, though :) Thanks, - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxa7YsACgkQ9CaO5/Lv0PD4KwCgpW4uc1fdeEgH9cLedoxy93WA njQAn3Vb57GRcTtJqNXuFkLG7bOcIPkc =mzJH -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org For additional commands, e-mail: users-h...@cocoon.apache.org
Re: argument type mismatch when using fn:replace
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 All, On 8/5/2010 12:57 PM, Christopher Schultz wrote: On 8/4/2010 5:09 PM, Thomas Ernest wrote: I remember having this problem, when I used the same version of Cocoon one year ago. I'm not 100% sure, but I mean fn:replace is a function belonging to XPath 2.0 [1] and Cocoon 2.1.11 integrates a Xalan implementing XPath 1.0 only. That would certainly explain the problem. My Cocoon has Xalan-2.7.1, which only supports XSLT 1.0 and XPath 1.0. It's odd that Xalan 2.7.1 is the latest version available. Is Xalan dead? Does Saxon replace it? It appears that no current version of Cocoon supports XSLT 2.0. Is that correct? Since neither Xalan nor Cocoon support XSLT/XPath 2.0 directly, is it okay to simply replace Xalan with another XSLT processor like Saxon? I'm unsure of what level of dependency Cocoon has on Xalan... hopefully, everything is done using the JAXP interfaces and not implementation-specific calls, but there may be some Xalan-specific configuration that Cocoon provides in order to grease the wheels a bit. Any suggestions that anyone has could be greatly appreciated. Thanks, - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxa780ACgkQ9CaO5/Lv0PDxJgCfZ3v+BcKYONZbve0WAdDBaD6n lScAoKuPuYz3z6spVlOlRjLml3C+8hb4 =aXy0 -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org For additional commands, e-mail: users-h...@cocoon.apache.org
Re: argument type mismatch when using fn:replace
I haven't used Cocoon in quite a while, but I remember that you can use Saxon instead of Xalan. A quick google search brings up the following old blog entry from Vadim: http://blog.reverycodes.com/archives/34.html Maybe that's a good start? /mde/ - Original Message From: Christopher Schultz ch...@christopherschultz.net To: users@cocoon.apache.org Sent: Thu, August 5, 2010 10:07:26 AM Subject: Re: argument type mismatch when using fn:replace -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 All, On 8/5/2010 12:57 PM, Christopher Schultz wrote: On 8/4/2010 5:09 PM, Thomas Ernest wrote: I remember having this problem, when I used the same version of Cocoon one year ago. I'm not 100% sure, but I mean fn:replace is a function belonging to XPath 2.0 [1] and Cocoon 2.1.11 integrates a Xalan implementing XPath 1.0 only. That would certainly explain the problem. My Cocoon has Xalan-2.7.1, which only supports XSLT 1.0 and XPath 1.0. It's odd that Xalan 2.7.1 is the latest version available. Is Xalan dead? Does Saxon replace it? It appears that no current version of Cocoon supports XSLT 2.0. Is that correct? Since neither Xalan nor Cocoon support XSLT/XPath 2.0 directly, is it okay to simply replace Xalan with another XSLT processor like Saxon? I'm unsure of what level of dependency Cocoon has on Xalan... hopefully, everything is done using the JAXP interfaces and not implementation-specific calls, but there may be some Xalan-specific configuration that Cocoon provides in order to grease the wheels a bit. Any suggestions that anyone has could be greatly appreciated. Thanks, - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxa780ACgkQ9CaO5/Lv0PDxJgCfZ3v+BcKYONZbve0WAdDBaD6n lScAoKuPuYz3z6spVlOlRjLml3C+8hb4 =aXy0 -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org For additional commands, e-mail: users-h...@cocoon.apache.org - To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org For additional commands, e-mail: users-h...@cocoon.apache.org
Re: argument type mismatch when using fn:replace
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark, On 8/5/2010 1:32 PM, Mark Eggers wrote: I haven't used Cocoon in quite a while, but I remember that you can use Saxon instead of Xalan. A quick google search brings up the following old blog entry from Vadim: http://blog.reverycodes.com/archives/34.html Maybe that's a good start? Thanks for the tip: I'll start there. It does look like switching from Xalan to Saxon is relatively painless, and, if the performance claims in that post are accurate, I may even get a faster product in the end. Thanks, - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxa9+0ACgkQ9CaO5/Lv0PB2pgCff9uHxt73O69IxhacUIEVkcK7 tWUAnRNDAJRJaIj4bzzMOl3iBUErbgTP =8rMS -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org For additional commands, e-mail: users-h...@cocoon.apache.org
