-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P3
-
Affects Version/s: 1.2.0
-
Component/s: xml
-
1.2.0
-
1.2.0
-
sparc
-
solaris_8
-
Verified
If I have
<?xml version="1.0"?>
<html>
<![CDATA[ <xml>This is not parsed</xml>]]> yet
</html>
and setCoalescing(true). I expect to get
<html>
<xml>This is not parsed</xml> yet
</html>
after DocumentBuilder.parser() is called.
Using crimson, it returns 1 ChildNode:<xml>This is not parsed</xml> yet
Using xerces2, it returns 3 childnode. node0: <cr>, node1: <xml>This is not parsed</xml>, node2: yet
According to setCoalescing definition, seems that crimson is doing the right thing.
To reproduce, execute torun in attched file.
<?xml version="1.0"?>
<html>
<![CDATA[ <xml>This is not parsed</xml>]]> yet
</html>
and setCoalescing(true). I expect to get
<html>
<xml>This is not parsed</xml> yet
</html>
after DocumentBuilder.parser() is called.
Using crimson, it returns 1 ChildNode:<xml>This is not parsed</xml> yet
Using xerces2, it returns 3 childnode. node0: <cr>, node1: <xml>This is not parsed</xml>, node2: yet
According to setCoalescing definition, seems that crimson is doing the right thing.
To reproduce, execute torun in attched file.