axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Hawkins (JIRA)" <>
Subject [jira] Updated: (AXISCPP-388) Programmatically set client-side handlers
Date Wed, 09 Feb 2005 18:00:11 GMT
     [ ]

John Hawkins updated AXISCPP-388:

    type: Improvement  (was: Bug)

> Programmatically set client-side handlers
> -----------------------------------------
>          Key: AXISCPP-388
>          URL:
>      Project: Axis-C++
>         Type: Improvement
>   Components: Handlers
>  Environment: n/a
>     Reporter: Fred Preston

> Client side handlers:
> Programmatically set client-side handlers (instead of either editing the WSDL or generated
code to specify the SOAP action name.
> At the moment there are two ways to ensure that your handler is called and
> that is:-
> Either:-
> Change the WSDL in the bindings section where you specify a <soap:operation soapAction=""
style="document"/>.  Now apparently you should not have to add the soap action here (as
it is not mandatory) and you should only have to add the operation in the client, but if you
do add it here, when you rebuild the client using WSDL2WS, you will get the soap action being
added to the stubs so that the handler will be called (if required) (an example would be "Calculator#add"
where 'Calculator' is the service name and 'add' is the operation you wish to call).  What
actually happens is that in the stub there is the call 'm_pCall->setTransportProperty(
SOAPACTION_HEADER, "");'.  The text in quotes is the soapAction.  Thus if there is nothing
in the WSDL then there will be nothing in the stub, so the handler will not be called.
> Or, in the generated stub created by the WSDL2WS tool, change the text in the call 'm_pCall->setTransportProperty(
SOAPACTION_HEADER, "")' to "Calculator#add".
> Neither is very satisfactory as you cannot set it in the client code because the
> stub will override the value set!

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message