Would it be possible for you to download the latest CVS code (2.2D6) and
see if you have the same problem there? There was quite a big design
change(DTM) in 2.2Dx, and we'd be curious to know if there is still an
issue with the new code. Please let us know one way or another if you get
a chance to run the latest code.
Thanks,
Myriam
Gerry
McDonough To: "'[EMAIL PROTECTED]'"
<gmcdonough@od <[EMAIL PROTECTED]>
bs.com> cc: (bcc: Myriam Midy/CAM/Lotus)
Subject: RE: String indexoutof range
07/17/01 11:39 exception
AM
Please respond
to xalan-dev
The version is xalan-j_2_0_1. I should say that I have not completely
localized the problem. I use the text blobs in 2 different contexts (one
is an edit mode, and one is a read mode), and the transformation succeeds
in one and not in the other. It turned out that my application's
requirements were for smaller text blobs, and that is how I am working
around the issue for now.
Thanks, Gerry
----------
From: [EMAIL PROTECTED]
Sent: Tuesday, July 17, 2001 10:18 AM
To: [EMAIL PROTECTED]
Subject: Re: String indexoutof range exception
Which version of Xalan are you using?
Myriam
Gerry
McDonough To:
"'[EMAIL PROTECTED]'"
<gmcdonough@od <[EMAIL PROTECTED]>
bs.com> cc: (bcc: Myriam
Midy/CAM/Lotus)
Subject: String indexoutof
range
07/17/01 11:20 exception
AM
Please respond
to xalan-dev
When transforming a Document with fairly large text nodes, between 30K and
40K, Xalan throws an exception with the message
"javax.xml.transform.TransformerException: String index out of range:
-40640". I think it is a function of the size, as I have not seen the
error since reducing the size of input that forms the text nodes. Are
there known size/transformation issues with Xalan? Has anyone else
encountered this behavior?
Thanks, Gerry
(See attached file: attecpg8.dat)
attecpg8.dat
