Petals BC SOAP

BC SOAP does not support empty SOAP action

View this issue in another formatViewView
- XML
- Word
- Printable

Details

Type: Bug
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: 4.0.4
Fix Version/s: 4.0.4
Component/s: None
Security Level: Public

Description:

Hide

It is possible to have soapAction="" in a WSDL. Consequently the BC SOAP must support incoming message with empty string as SOAP action. It does not work currently.

[Petals.Container.Components.petals-bc-soap]-FINE 2010-10-20 15:12:19,780 Receiving a message from Axis2 engine
[Petals.Container.Components.petals-bc-soap]-FINE 2010-10-20 15:12:19,780 Processing the incoming SOAP message
[Petals.Container.Components.petals-bc-soap]-FINEST 2010-10-20 15:12:21,912 soapAction found in the incoming message :
[Petals.Container.Components.petals-bc-soap.jetty]-FINEST 2010-10-20 15:13:04,399 RESPONSE /petals/services/Talend 500

Show
It is possible to have soapAction="" in a WSDL. Consequently the BC SOAP must support incoming message with empty string as SOAP action. It does not work currently. [Petals.Container.Components.petals-bc-soap]-FINE 2010-10-20 15:12:19,780 Receiving a message from Axis2 engine [Petals.Container.Components.petals-bc-soap]-FINE 2010-10-20 15:12:19,780 Processing the incoming SOAP message [Petals.Container.Components.petals-bc-soap]-FINEST 2010-10-20 15:12:21,912 soapAction found in the incoming message : [Petals.Container.Components.petals-bc-soap.jetty]-FINEST 2010-10-20 15:13:04,399 RESPONSE /petals/services/Talend 500

Environment:

os:all

Activity

Descending order - Click to sort in ascending order

There are no comments yet on this issue.

People

Assignee:

noddoux

Reporter:

noddoux
Watchers:

0

Dates

Created:

Wed, 20 Oct 2010 - 15:40:27 +0200

Updated:

Wed, 20 Oct 2010 - 15:45:18 +0200

Resolved:

Wed, 20 Oct 2010 - 15:45:18 +0200