cancel
Showing results for 
Search instead for 
Did you mean: 

Receiver SOAP AXIS adapter SOAP body missing.

Former Member
0 Kudos

Hi,

I am trying to configure the receiver SOAP AXIS adapter on PI 7.1. SOAP Axis is used to pass the USER NAME TOKEN to the Web service

I call a Web service and want to pass this as the payload

<ns1:Drivers xmlns:ns1="http://www.xatanet.net/XataNetWebService/DriverManager">

<ns1:DriverImportDataObjectV2>

<ns1:InternalElementID>1</ns1:InternalElementID>

<ns1:Action>4</ns1:Action>

<ns1:OrganizationID>2</ns1:OrganizationID>

<ns1:DriverID>3</ns1:DriverID>

</ns1:DriverImportDataObjectV2>

</ns1:Drivers>

The Web service gets to SOAP request with additional security header informartion, but without a SOAP Body

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<soapenv:Header>

<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" soapenv:mustUnderstand="1"><wsse:UsernameToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="UsernameToken-741548613"><wsse:Username>sysco\dev</wsse:Username><wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">environment</wsse:Password></wsse:UsernameToken></wsse:Security></soapenv:Header><soapenv:Body /></soapenv:Envelope>

My settings for AXIS are

No Header

No attachements

Payload Extraction = bodyChild

i have set my outbound handler java:com.sap.aii.axis.xi.XI30OutboundHandler with the paramter payload = bodyChild.

Can anyone help here? What can be the problem.

Regards,

Abhishek

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Abhishek,

This is very strange.

Did you put the handlers in the right oder and correctly configured, as described in the Axis adapter FAQ note? And which version of wss4j are you using?

If the configuration appears correct but you still have this problem, you can try the following things.

1. turn on the trace level of org.apache.axis and org.apache.ws to DEBUG. Send a message and see what it writes.

2. another thing you can do it to remove the ws handler and send a message with the same DEBUG trace option.

Both traces will include the transmitted SOAP message plus all the detailed processing debug statements.

You can probably find some relevant information to this problem.

Best regards, Yza

Answers (0)