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

SOAP gateway is requiring the WSDL message name to match the operation name

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Done
    • 0.1
    • 0.2
    • core
    • None

    Description

      See the attached .zip example.

      This exception is raised when the example is deployed to Switchyard on AS7:

      <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
      <SOAP-ENV:Header/>
      <SOAP-ENV:Body>
      <SOAP-ENV:Fault>
      <faultcode>SOAP-ENV:Server</faultcode>
      <faultstring>Invalid input SOAP payload localNamePart for service operation 'sayHello' (service 'HelloService'). Port defines operation localNamePart as 'HelloWorld_sayHello'. Actual localNamePart on input SOAP message 'sayHello'.</faultstring>
      </SOAP-ENV:Fault>
      </SOAP-ENV:Body>
      </SOAP-ENV:Envelope>

      Note from Keith:

      The element name should match in doc/lit, but the message name should just be metadata for the WSDL itself.

      Attachments

        Issue Links

          Activity

            People

              mageshbk_jira Magesh Bojan (Inactive)
              ldimaggi@redhat.com Len DiMaggio
              Archiver:
              ranumula@redhat.com Raju Anumula

              Dates

                Created:
                Updated:
                Resolved:
                Archived: