Re: IWS - Generated WSDL

It does not need to be set. But if your client applications always set
that to some value, you would need to edit the WSDL by going to the web
service properties link and selecting the WSDL tab.

Otherwise, client applications usually do what is specified in the WSDL,
and thus client application would pass the following HTTP header on the
request:

SOAPAction: ""




"WEB400" <web400-bounces@xxxxxxxxxxxx> wrote on 07/31/2017 05:02:38 AM:

From: Eric <send2et@xxxxxxxxx>
To: "Web Enabling the IBM i (AS/400 and iSeries)" <web400@xxxxxxxxxxxx>
Date: 07/31/2017 05:03 AM
Subject: [WEB400] IWS - Generated WSDL
Sent by: "WEB400" <web400-bounces@xxxxxxxxxxxx>

Hi,

I noticed that within the generated WSDL after setting up a IWS service,
the soapAction is no longer specified within the binding element. Any

ideas?

Is this something that I need to configure when setting up the IWS

server?

<binding name="CUSTOMERServicesPortBinding" type="tns:CUSTOMERServices">
<soap:binding style="document" transport="
http://schemas.xmlsoap.org/soap/http"/>
<operation name="searchcustomer">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>

I would expect that the soapAction would be searchcustomer which is the
same as the operation name?

Many thanks,
Eric
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing

list

To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.