Vadim Gritsenko [EMAIL PROTECTED] writes:
snip/
Has anyone managed to get around this and get Cocoon 2.1.4 working
using Saxon 7.9 as the default XSLT processor?
Saxon 7.9 has different XPath API - you'll need CVS version of
excalibur-xmlutils.
Ok, I give up. Where the %@[EMAIL
Hunsberger, Peter wrote:
Vadim Gritsenko [EMAIL PROTECTED] writes:
snip/
Has anyone managed to get around this and get Cocoon 2.1.4 working
using Saxon 7.9 as the default XSLT processor?
Saxon 7.9 has different XPath API - you'll need CVS version of
excalibur-xmlutils.
Ok, I
implementation cannot be updated (it's read-
only).
Has anyone managed to get around this and get Cocoon 2.1.4 working using
Saxon 7.9 as the default XSLT processor?
If so, how did you do this? Did you replace the Saxon DOM implementation
(and if so, how)?
I remember having such problems with older
#
# X-posted to the Saxon list as well.
#
# I remember having such problems with older versions of
# Saxon, and the
# culprit was the AElfred parser that comes bundled with
# Saxon which is
# limited to saxon's needs (hence why it's read-only).
AElfred is a SAX parser only, it does
On Wed, 2004-03-24 at 15:16, Andrzej Jan Taramina wrote:
Sylvain:
X-posted to the Saxon list as well.
I remember having such problems with older versions of Saxon, and the
culprit was the AElfred parser that comes bundled with Saxon which is
limited to saxon's needs (hence why
read-
only).
Has anyone managed to get around this and get Cocoon 2.1.4 working using
Saxon 7.9 as the default XSLT processor?
If so, how did you do this? Did you replace the Saxon DOM implementation
(and if so, how)?
Thanks!
Andrzej Jan Taramina
Chaeron Corporation: Enterprise System
