Never mind. When I put together a stand-alone test case to demonstrate
the problem I couldn't reproduce it. I dug further into the
application code to see where the differences were and discovered that
it was reading the XML document file in from disk using
BufferedReader.readLine. The line feeds were therefore getting
stripped out when loading from disk rather than in the getData call.
Thanks for the help - it got me on the right track anyway.
-- Mike Rawlins
---- Michael Glavassevich
wrote: >Hi Mike, > >Off the top of my head, I can't think of a
reason why that would happen. >Do you have a stand-alone test which
you could share that reproduces this? > >Thanks. >
>Michael Glavassevich >XML Parser Development >IBM Toronto Lab
>E-mail: mrglavas@xxxxxxxxxx >E-mail: mrglavas@xxxxxxxxxx >
>Mike Rawlins wrote on 08/14/2007
04:40:08 PM: > >>Michael, >>Thanks for the
suggestion, that doesn't seem to be it. The debugger >>shows both
CR and LF removed from the CDATASection. It doesn't >>matter
whether the file has CR/LF as line terminators or just LF. >>Mike
>> >>-- >>Mike Rawlins >> >>---- Michael
Glavassevich wrote: >>>Hi Mike, >>> >>>XML
parsers are required to normalize [1] line breaks (CR LF -> LF).
>Are >>>you sure that's not what's happening? >>>
>>>Thanks. >>> >>>[1]
http://www.w3.org/TR/2006/REC-xml-20060816/#sec-line-ends >>>
>>>Michael Glavassevich >>>XML Parser Development
>>>IBM Toronto Lab >>>E-mail: mrglavas@xxxxxxxxxx
>>>E-mail: mrglavas@xxxxxxxxxx >
>---------------------------------------------------------------------
>To unsubscribe, e-mail: j-users-unsubscribe@xxxxxxxxxxxxxxxxx >For
additional commands, e-mail: j-users-help@xxxxxxxxxxxxxxxxx >
|
Try Searching:
servers, voip, java, networking, microsoft ...
|
|
|
|