RFR: 8081392: getNodeValue should return NULL value for Element nodes (original) (raw)
huizhe wang huizhe.wang at oracle.com
Thu May 28 16:50:40 UTC 2015
- Previous message: RFR: 8081392: getNodeValue should return NULL value for Element nodes
- Next message: Why isn't Object.notify() a synchronized method?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Aleksej,
Thanks for the quick action! The changes are good to me.
Best, Joe
On 5/28/2015 8:33 AM, Aleksej Efimov wrote:
Hi,
Please, review JDK9 fix [1] for a bug [2] in 'getNodeValue' JAXP function: According to w3c [3] getNodeValue should return 'null' value for Element nodes. This behavior was changed by JDK-8032908 [4] fix - in current implementation the node content is returned. To address this issue the JDK-8032908 fix was reverted and 'getTextContent' function was modified properly to address issue reported by JDK-8032908. JDK-8032908 test was modified to test that 'getNodeValue' returns 'null' for Element nodes. DocumentExtFunc test was modified to use 'getTextContent' instead of 'getNodeValue' for node content retrival. No related test failures on local and JPRT builds were observed. With Best Regards, Aleksej [1] http://cr.openjdk.java.net/~aefimov/8081392/9/00 [2] https://bugs.openjdk.java.net/browse/JDK-8081392 [3] http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/core.html#ID-1950641247 [4] https://bugs.openjdk.java.net/browse/JDK-8032908
- Previous message: RFR: 8081392: getNodeValue should return NULL value for Element nodes
- Next message: Why isn't Object.notify() a synchronized method?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]