Hi,
We're using Xalan (2.6.0) with heavy use of Java extensions (especially the e-xslt extensions) and from time to time, we've been noticing document being rendered with odd corruptions which render them invalid XML fragments.
At other times, part of the source document makes its way into the translated output!
Some of documents being translated are around the 1meg mark - although I don't really think that this should cause too much trouble.
We also make quite extensive use of namespaces - sometimes up to a dozen.
At first I attributed this to a corrupt store, but I've recently re-implemented the persistent store using a different cache store, and still have this trouble. It may well be a Xalan issue, but I thought I should ask here first.
Some specifics:
Xalan 2.6.0 (although 2.5.2 exhibited the same issues)
Xerces 2.6.2
NOT using XSLTC
Documents ~1meg
Using Xalan extension elements: evaluate, dyn:map
Problem occurs erratically, not just under high load.
Raw input source makes its way into output.
We have up to a 5 level hierarchy in our document structure.
Has anyone else encountered a similar problem?
Thanks,
Corin
Corin Moss
Lead Developer
TVNZ Interactive
+64 9 916 7367
+64 21 403 054
[EMAIL PROTECTED]
================================================================ CAUTION: This e-mail and any attachment(s) contains information that is intended to be read only by the named recipient(s). It may contain information that is confidential, proprietary or the subject of legal privilege. This information is not to be used by any other person and/or organisation. If you are not the intended recipient, please advise us immediately and delete this e-mail from your system. Do not use any information contained in it. ================================================================ For more information on the Television New Zealand Group, visit us online at http://www.tvnz.co.nz ================================================================ |
