RFR: 8336815: Several methods in java.net.Socket and ServerSocket do not specify behavior when already bound, connected or closed [v6]
Jaikiran Pai
jpai at openjdk.org
Wed Jul 24 11:37:13 UTC 2024
> Can I please get a review of this change which updates the specification of a few methods in `java.net.Socket` and `java.net.ServerSocket` classes to specify the `IOException` that the implementation currently already throws?
>
> This is merely a doc update and doesn't change the implementation.
>
> Given that these exceptions can now be asserted, a new jtreg test has been introduced to verify the exceptions thrown from these APIs. The test passes. tier testing is currently in progress. I'll open a CSR shortly.
Jaikiran Pai has updated the pull request incrementally with one additional commit since the last revision:
tiny adjustments to the javadoc
-------------
Changes:
- all: https://git.openjdk.org/jdk/pull/20268/files
- new: https://git.openjdk.org/jdk/pull/20268/files/1fb30002..12454ecd
Webrevs:
- full: https://webrevs.openjdk.org/?repo=jdk&pr=20268&range=05
- incr: https://webrevs.openjdk.org/?repo=jdk&pr=20268&range=04-05
Stats: 2 lines in 2 files changed: 0 ins; 0 del; 2 mod
Patch: https://git.openjdk.org/jdk/pull/20268.diff
Fetch: git fetch https://git.openjdk.org/jdk.git pull/20268/head:pull/20268
PR: https://git.openjdk.org/jdk/pull/20268
More information about the net-dev
mailing list