Petals BC SOAP

SOAPAction filled in provider mode, even if SOAPAction not set in WSDL

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 4.3.0
  • Fix Version/s: 4.3.4, 4.3.5
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    If the SOAPAction is missing or defined to an emty value into the WSDL of an external service provider, the Petals BC SOAP generates a SOAPAction set to a value as 'urn:<operation>', instead of an empty value. And so, the request is rejected by the external web-service because the SOAPAction has not the expected value.

    It should be better if output SOAPAction stay same than in WSDL.

    Show
    If the SOAPAction is missing or defined to an emty value into the WSDL of an external service provider, the Petals BC SOAP generates a SOAPAction set to a value as 'urn:<operation>', instead of an empty value. And so, the request is rejected by the external web-service because the SOAPAction has not the expected value. It should be better if output SOAPAction stay same than in WSDL.
  • Environment:
    RHEL 6.4

People

Dates

  • Created:
    Tue, 4 Aug 2015 - 18:01:17 +0200
    Updated:
    Mon, 7 Sep 2015 - 16:18:13 +0200
    Resolved:
    Mon, 7 Sep 2015 - 16:18:12 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.