-
Bug
-
Resolution: Fixed
-
P3
-
9
-
b14
In JDK 8, we introduced a JDK-internal service provider to allow the implementation of Properties.loadFromXML and storeToXML use alternative XML parsers.
JDK 8 builds use a service provider implementation based on JAXP. Builds of the compact1 profile (which doesn't define any XML APIs) use the small UKit parser.
This bug is submitted to continue this effort and to change Properties to consistently use the UKit parser. A concern when we originally brought in the UKit parser is that test coverage in this area was weak, and additionally the Properties specification wasn't clear on the encodings that the implementation is required to support. The Java SE API specification was clarified via
- relates to
-
JDK-8043592 The basic XML parser based on UKit fails to read XML files encoded in UTF-16BE or LE
-
- Closed
-
-
JDK-8043929 The basic XML parser fails with a NPE or UEE if encoding is null or empty
-
- Closed
-
-
JDK-8276207 Properties.loadFromXML/storeToXML works incorrectly for supplementary characters
-
- Closed
-
-
JDK-8000354 (props) Properties.storeToXML/loadFromXML need to allow for alternative implementations
-
- Resolved
-
-
JDK-8004371 (props) Properties.loadFromXML needs small footprint XML parser as fallback when JAXP is not present
-
- Closed
-