-
Bug
-
Resolution: Fixed
-
P4
-
None
-
b65
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8082178 | emb-9 | Andy Herrick | P4 | Resolved | Fixed | b65 |
| JDK-8086366 | 8u65 | Andy Herrick | P4 | Resolved | Fixed | b01 |
| JDK-8077540 | 8u60 | Andy Herrick | P4 | Resolved | Fixed | b15 |
| JDK-8137492 | emb-8u65 | Unassigned | P4 | Resolved | Fixed | b01 |
| JDK-8079910 | emb-8u60 | Andy Herrick | P4 | Resolved | Fixed | team |
The new XMLParser will no longer trim CDATA content, so that a node of:
<foo> </foo> actaully has a sub element named " ".
This has no effect on actuall running, but several test cases in XMLParserTest fail when either just space exists between start and end element and then XMLNode is compared such as:
<jnlp>/n</jnlp> is compared to see if it is equal to <jnlp/>
simple fix is to remove spaces and newlines explicitly put between tags in test
<foo> </foo> actaully has a sub element named " ".
This has no effect on actuall running, but several test cases in XMLParserTest fail when either just space exists between start and end element and then XMLNode is compared such as:
<jnlp>/n</jnlp> is compared to see if it is equal to <jnlp/>
simple fix is to remove spaces and newlines explicitly put between tags in test
- backported by
-
JDK-8077540 XMLParserTest unit test failure.
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-