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

Activity

Christophe DENEUX made changes - Tue, 4 Aug 2015 - 18:03:56 +0200
Field Original Value New Value
Status New [ 10000 ] Open [ 10002 ]
Priority Major [ 3 ]
Assignee Nicolas Oddoux [ noddoux ] Christophe DENEUX [ cdeneux ]
Christophe DENEUX made changes - Thu, 6 Aug 2015 - 10:31:23 +0200
Description Call for BC in provider mode to an external Web service with empty SoapAction set, is done with a default SOAPAction which is not supported by external application.

It should be better if output SOAPAction stay same than in WSDL.
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.
Christophe DENEUX made changes - Thu, 6 Aug 2015 - 10:31:43 +0200
Description 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.
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.
Christophe DENEUX made changes - Thu, 6 Aug 2015 - 10:32:21 +0200
Description 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.
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.
Christophe DENEUX made changes - Thu, 6 Aug 2015 - 10:39:32 +0200
Status Open [ 10002 ] In Progress [ 10003 ]
Christophe DENEUX made changes - Thu, 6 Aug 2015 - 16:04:02 +0200
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 4.3.4 [ 10557 ]
Resolution Fixed [ 1 ]
Christophe DENEUX made changes - Thu, 6 Aug 2015 - 16:04:21 +0200
Status Resolved [ 10004 ] Open [ 10002 ]
Resolution Fixed [ 1 ]
Christophe DENEUX made changes - Thu, 3 Sep 2015 - 15:03:42 +0200
Status Open [ 10002 ] In Progress [ 10003 ]
Christophe DENEUX made changes - Thu, 3 Sep 2015 - 15:04:21 +0200
Fix Version/s 4.3.5 [ 10572 ]
Christophe DENEUX made changes - Mon, 7 Sep 2015 - 16:18:13 +0200
Status In Progress [ 10003 ] Resolved [ 10004 ]
Resolution Fixed [ 1 ]

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