Uploaded image for project: 'SwitchYard'
  1. SwitchYard
  2. SWITCHYARD-2195

SOAP Binding: Server Port field no longer manages colon properly

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: 2.0
    • Fix Version/s: 2.0
    • Component/s: tooling
    • Labels:
      None

      Description

      While doing some testing, Keith discovered that the SOAP Binding's "Server Port" field no longer managed the colon between host and port correctly.

      He had this to say via e-mail:

      Looks like there may be a regression in the SOAP binding wizard / property sheet in the 'Server Port' field. This field has the format:

      [hostname]:port

      The hostname value is optional and is not commonly used, which means that we normally set this field to something like this:

      :18080

      Brian - I think you added some logic some time back to automatically insert the ':' if it was not specified by the user, but that seems to be gone now.

      Forgot to mention that I'm open to changing the way we handle this if you think it's better to take a different approach. The ":" must be in switchyard.xml for this field, but at the UI level, we have options:

      1) Require the user to enter it. I imagine people will forget or simply not know it's required though.
      2) Put the input field filter back in place that automatically adds a ":" to the value in the input field.
      3) Don't add a ":" to the input field if it's not specified, but do add it to switchyard.xml when the field is persisted. This requires a bit more sophistication in parsing the value inside the UI.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                bfitzpat Brian Fitzpatrick
                Reporter:
                bfitzpat Brian Fitzpatrick
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: