The saga continues... > -----Original Message----- > From: Lars Huttar [mailto:[EMAIL PROTECTED] > Sent: Friday, July 30, 2004 10:50 AM > To: [EMAIL PROTECTED] > Subject: RE: Error: The Saxon DOM cannot be updated > > > > -----Original Message----- > > From: Lars Huttar [mailto:[EMAIL PROTECTED] > > Sent: Friday, July 30, 2004 9:07 AM > > To: Cocoon Users List (E-mail) > > Subject: Error: The Saxon DOM cannot be updated > > > > > > Dear Cocoonists, > > > > I'm getting a strange error when using Saxon with Cocoon. > > Versions: Tomcat 4.1, Cocoon 2.1.2, Saxon 7.9 > > Summary of problem: I get an error "The Saxon DOM cannot be updated" > > at a point in the pipeline where Saxon isn't supposed to be > > involved. > > FWIW, when I try the same thing with Cocoon 2.1.5 under Jetty, > there is no error. > > So, that is a possible workaround, but I'd rather not have to > migrate our development server to Cocoon 2.1.5 and/or Jetty > at this point if it can be avoided.
Actually no it's not a possible workaround; I don't get the Saxon DOM error, but then, if I try using an XSLT (WD) 2.0 stylesheet, I get the error "Could not find function: current-group" which seems to indicate that I'm not using Saxon at all. (I have tested the XSLT 2.0 stylesheet outside of Cocoon with the same Saxon jar, and it works fine.) Since the whole point of using Saxon was to be able to use XSLT 2.0 features, I still haven't achieved the goal. Suggestions? Is anyone using Cocoon with Saxon 7 or 8? My Cocoon 2.1.5 xslt transformer configuration is basically the same as what I described above for Cocoon 2.1.2. Lars --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
