-----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: [email protected] For additional commands, e-mail: [email protected]
