Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-2966

add an unresolvedDestinationAddress property to OutboundSocketBinding

    Details

      Description

      The outbound-socket-config resource allows to specify an host but the corresponding OutboundSocketConfig always returns a resolved (on the server) InetAddress in its #getDestinationAddress() method.

      On hosted environment such as OpenShift, the domain name resolution may be different from the hosted server than from the client so that the resolved IP address may be different in the two cases.

      There are use cases where we need to retrieve the unresolved destination address specified in the resource. For example, the messaging connectors must know the hostname of the server but the name resolution must be done on the client side, not on the server side.

      This enhancement would add a getUnresolvedDestinationAddress() method to OutboundSocketConfig(), deprecates the current getDestinationAddress() and delegates it to a new getResolvedDestinationAddress() method

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                jmesnil Jeff Mesnil
                Reporter:
                jmesnil Jeff Mesnil
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: