The SOAPAction in the HTTP header is only relevant for handlers in Axis
C++. It is not a WSDL requirement to have anything set, and "" has special
meaning. Some service engines do require SOAPAction to be set like .net.
The only tests which might possibly fail are tests which use handlers, or
tests run against a service engine which requires SOAPAction to be set.
If SOAPAction is given as a command line option, then the clients will have
to be written/changed to use this new command line parameter. Would it not
easier to change the WSDL for the tests which require it to have a
SOAPAction set in the WSDL? This would exclued any test which is designed
to test the setTransportProperty("SOAPAction", ...
Regards,
Andrew Perry
IBM Web Services Client for C/C++
[EMAIL PROTECTED]
Mail Point 127
IBM UK Laboratories. Hursley Park, Winchester, Hants. SO21 2JN
Tel. Internal 249828 External + 44 (0)1962 819828
Fax. + 44(0)1962 818080
"Dushshantha Chandradasa" <[EMAIL PROTECTED]> wrote on 22/03/2005
13:04:37:
> Hi All,
>
> When running the test framework, some clients are not running
> because some client stubs are not setting the SOAP Action correctly.
> So I would like to suggest that the SOAPAction is set in the client
> code calling setTransportProperty() method of the stub ( we use this
> option locally very successfully )
>
> Ex: ws.setTransportProperty(âSOAPActionâ, "Calculator#add");
> iResult = ws.add(i1, i2);
>
>
> Or to give the SOAPAction as a command line option
>
> Regards,
>
> Marcus Dushshantha Chandradasa
> Associate Software Engineer
> Virtusa (Pvt) Ltd.
> [EMAIL PROTECTED]
> Mob: 0714867441
>
>
>
