Thomas Börkel wrote:
> Clearly, the XML is damaged. And it's not the Transformer's
> fault, because if you iterate through the DOM, you see that
> the 2nd CDATA node really has the wrong data.
>
> Anyone any idea, please? Am I doing something wrong?
This looks like a bug in Xerces 2.0.0. But th
> Sent: Dienstag, 26. Februar 2002 12:54
> To: Xerces Mailinglist
> Subject: Bad bug in Xerces?
>
>
> HI!
>
> Consider the following XML, which is being built with
> dbf = DocumentBuilderFactory.newInstance();
> db = dbf.newDocumentBuilder();
> doc = db.pars
is already fixed, see bugzilla !
-Original Message-
From: Thomas Börkel [mailto:[EMAIL PROTECTED]
Sent: dinsdag 26 februari 2002 12:54
To: Xerces Mailinglist
Subject: Bad bug in Xerces?
HI!
Consider the following XML, which is being built with
dbf = DocumentBuilderFactory.newInstance
Hi Thomas,
>
>
> Clearly, the XML is damaged. And it's not the Transformer's fault, because if
you iterate through the DOM, you see that the 2nd CDATA node really has the
wrong data.
>
>
> Anyone any idea, please? Am I doing something wrong?
I think this was a bug, which was recently fixe
nside. Do I have to
compile and build this jar-file myself from the current sources? Couldn't this
be integrated into the nightly build process (just wondering)?
> -Original Message-
> From: Thomas Börkel
> Sent: Dienstag, 26. Februar 2002 12:54
> To: Xerces Mailinglist
HI!
Consider the following XML, which is being built with
dbf = DocumentBuilderFactory.newInstance();
db = dbf.newDocumentBuilder();
doc = db.parse(new InputSource(new StringReader(text))):
If you write out the document after this with
streamResult = new StreamResult(new StringWriter());
tra
