Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-6573503

Socket(raddr, rport, laddr, lport) allows null as laddr that spec doesn't reflect

    Details

    • Type: Enhancement
    • Status: Closed
    • Priority: P3
    • Resolution: Not an Issue
    • Affects Version/s: 7
    • Fix Version/s: 7
    • Component/s: core-libs
    • Labels:
    • Subcomponent:
    • CPU:
      generic
    • OS:
      generic

      Description

      For java.net.Socket class
       constructor
          Socket(InetAddress address, int port,
                 InetAddress clientAddress, int clientPort)

      allows passing (InetAddress)null as clientAddress. ( in JDK 5, JDK 6, JDK 7 )

      It looks like in this case the system will pick up a valid local address for create/bind.
      Specification for this constructor doesn't reflect this.
      The same promlem is in spec for javax.net.ssl.SSLSocket class for similar constructor.

      For instance spec in Socket class for method
       void bind(SocketAddress bindpoint)
      clearly says that:
      "If the address is null, then the system will pick up an ephemeral port and a valid local address to bind the socket."
      It will be good idea to have the similar info in spec concerning constructor
         Socket(InetAddress address, int port, InetAddress clientAddress, int clientPort)

      and the same for class SSLSocket:
         SSLSocket(InetAddress address, int port, InetAddress localAddr, int localPort)
      ( See CR 6571950 )

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jccollet Jean-Christophe Collet (Inactive)
                Reporter:
                dgubkin Dmitriy Gubkin (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Imported:
                  Indexed: