-
Bug
-
Resolution: Fixed
-
P2
-
11
-
b20
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8206777 | 12 | Brian Burkhalter | P2 | Resolved | Fixed | team |
JDK-8206554 | 11.0.1 | Brian Burkhalter | P2 | Resolved | Fixed | b01 |
As part of new test development for the CSR : JDK-8196350
It's been observed that specification mismatch to the behavior.
java.io.Reader
Specification :
nullReader()
"While the stream is open, the read(), read(char[]), read(char[], int, int), read(Charbuffer), ready()), skip(long), and transferTo() methods all behave as if end of stream has been reached. After the stream has been closed, these methods all throw IOException."
Actual result :
invoking ready() after closing the nullReader does not throw IOException.
2. "The mark() method does nothing, and the reset() method throws IOException."
Actual Result :
Invoking the mark() throws IOException.
Code snipped attached to demonstrate this.
It's been observed that specification mismatch to the behavior.
java.io.Reader
Specification :
nullReader()
"While the stream is open, the read(), read(char[]), read(char[], int, int), read(Charbuffer), ready()), skip(long), and transferTo() methods all behave as if end of stream has been reached. After the stream has been closed, these methods all throw IOException."
Actual result :
invoking ready() after closing the nullReader does not throw IOException.
2. "The mark() method does nothing, and the reset() method throws IOException."
Actual Result :
Invoking the mark() throws IOException.
Code snipped attached to demonstrate this.
- backported by
-
JDK-8206554 Reader:nullReader() spec does not match the behavior
-
- Resolved
-
-
JDK-8206777 Reader:nullReader() spec does not match the behavior
-
- Resolved
-
- csr for
-
JDK-8205090 Update of the Reader:nullReader() spec for the mark() method
-
- Closed
-
- links to