Thank you everyone for your responses.
I have also possed the same question on the Cocoon users list but as I have different e-mail addresses for the two list cross-posting has to be done manually.
As it seems there is no obvious change that may have contributed to the afore mentioned behaviour I will package-up an example Cocoon webapp with log message etc. and pass this over to the Cocoon list.
Thanks again for the input.
> and run it once with Saxon 8.6 and once with Saxon 8.7.1.. .
> If the two documents resulting are the same, then file a bug
> on the Cocoon users mailing list (it's not a Saxon problem),
> otherwise, it's a problem with Saxon doing something weird in
> the XSLT translation (but I don't think so, seriously).
This problem (unless it's some crazy user error) is almost certainly an
interaction problem, relating to the way in which Cocoon is calling Saxon.
Generally in such cases I think it works best to create clear reproducible
evidence of the problem, and then raise the bug with the "calling"
application - Cocoon - who can then raise a bug report on the "called"
application if appropriate.
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
saxon-help mailing list