On 27/05/14 15:56, mark.reinh...@oracle.com wrote:
2014/5/26 20:01 -0700, michael.x.mcma...@oracle.com:
I think it should be throwing a SocketException rather than a
NotYetBoundException to be consistent with ServerSocket.accept()
No, NotYetBoundException is the correct exception here. The NIO
exception hierarchy was intentionally designed to be richer than
just "SocketException". Consistency with the exceptions thrown
by the original java.net APIs is an anti-goal.
- Mark
Hi Mark,
The point was clarified on a separate conversation on net-dev.
The method in question refers to the channel's server socket adapter
(ie an instance of java.net.ServerSocket) rather than the channel itself.
What I overlooked was that the exception is being caught correctly
and converted to the right exception expected by ServerSocket.
Michael.
