axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Roshan Weerasuriya <>
Subject Re: SOAP Header manipulation & Handler API
Date Tue, 02 Mar 2004 14:23:37 GMT
hi Jean-Yves,

 >But I didn't find any APIs for passing or receiving parameters from this 
WSDL binding file

Can you just explain a bit more this scenario. i.e What you mean here, with 
little bit detail.
Currently I am trying to figure out what you mean exactly. So your help to 
clarify this issue a bit more is greatly appreciated.


At 05:23 PM 3/1/2004 +0000, you wrote:

>Hi Roshan,
>I update to the last CVS version of the code. I made some tests with the 
>new Handler writing API for SOAP Headers. It works fine for client runtime 
>interaction (ss your sample show). But I didn't find any APIs for passing 
>or receiving parameters from this WSDL binding file. Here an example :
>   <wsdl:binding name="StockServiceSoapBinding" type="intf:StockService">
>     <wsdlsoap:binding style="document" 
> transport=""/>
>     <wsdl:operation name="getLastSellPrice">
>       <wsdlsoap:operation soapAction=""/>
>       <wsdl:input>
>         <wsdlsoap:body use="literal" parts="input"/>
>         <wsdlsoap:header message="intf:getLastSellPriceRequest" 
> part="request_header_param1" use="literal"/>
>         <wsdlsoap:header message="intf:getLastSellPriceRequest" 
> part="request_header_param2" use="literal">
>            <wsdlsoap:headerfault message="intf:getLastSellPriceRequest" 
> part="request_header_fault" use="literal"/>
>         </wsdlsoap:header>
>       </wsdl:input>
>       <wsdl:output>
>         <wsdlsoap:body use="literal" parts="output"/>
>         <wsdlsoap:header message="intf:getLastSellPriceResponse" 
> part="response_header" use="literal"/>
>       </wsdl:output>
>     </wsdl:operation>
>   </wsdl:binding>
>For this maybe we can add a dedicated HeaderBlock (HeaderParamBlock for 
>example) with the same API we have in the Call.h interface. But am not 
>sure about that (it could involve a huge code duplication when 
>deserialazing). An other way if doing this is to add a 
>SetSoapSerializer/SetSoapDeserializer setter but I don't know if it is 
>possible (the main problem is how to get the stream contents).

View raw message