Re: WSE2.0 does not honor REPLYTO and FAULTO in SoapEnvelope?

Hi Sidd... many thanks for the clarification. I've actually implemented a
SoapClient and SoapService now which works well. However, the SOAP message
generated by the SoapClient does not contain any of the WS header
information (WS-Addressing or WS-Sec)? Do you know if I need to implement my
own "default" pipeline for SoapClient?


--
Pete Wood
Contact me at http://www.webserviceshelp.org for more help
_________________________________________________________


"Sidd" <ElCid@xxxxxxxxxxx> wrote in message
news:eR1y8agaFHA.3040@xxxxxxxxxxxxxxxxxxxxxxx
> Hi Pete,
>
> Is your services an ASP.NET web service? or a SoapService? I'm
> guessing
> that it is an ASP.NET web service, in which case WSE does not
> automatically
> send message to the ReplyTo.
>
> In order to use ReplyTo and FaultTo, you must use have your service
> inherit from SoapService. If you use HTTP, then these are strictly 2 was
> messages, request-response. Since ASMX is using http, by setting ReplyTo,
> you are indicating that you want to create a new message (the reply
> message)
> at the server so that it can send it to the reply to endpoint. This is
> only
> supported for tcp.
>
> Thanks,
>
> Sidd [MSFT]
>
> "Pete Wood" <wood_pete@xxxxxxxxxxx> wrote in message
> news:eJUADbiZFHA.3048@xxxxxxxxxxxxxxxxxxxxxxx
>> All...
>>
>> In playing around with WSE and populating the REPLYTO and/or FAULTO
> element
>> of the address, I find that WSE2 does not route the message to the
> supplied
>> URI. I have the configuration <allowRedirectedResponses enabled="true"
>> />
>> in the Web.Config, but the web service always sends the response back
>> to
>> the initiating web service. Do I need to specifically code a SoapSender
> in
>> the web service to send the response back to the URI in the supplied
> REPLYTO
>> field? I would have expected the dispatcher in WSE2.0 to take care of
> that
>> for me!
>>
>> --
>> Pete Wood
>> Contact me at http://www.webserviceshelp.org for more help
>> _________________________________________________________
>>
>>
>>
>
>


.

Relevant Pages

  • chunking with DimeAttachment
    ... I am currently implementing a web service which has to ... I am using TCP and SoapService ... DimeAttachment dime = new DimeAttachment ... My Soapclient method looks like this ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: WSE2.0 does not honor REPLYTO and FAULTO in SoapEnvelope?
    ... > SoapClient and SoapService now which works well. ... > Pete Wood ... >> Is your services an ASP.NET web service? ... >> send message to the ReplyTo. ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: WSE2.0 does not honor REPLYTO and FAULTO in SoapEnvelope?
    ... Is your services an ASP.NET web service? ... In order to use ReplyTo and FaultTo, you must use have your service ... inherit from SoapService. ... > In playing around with WSE and populating the REPLYTO and/or FAULTO ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: UserNameToken with SendNone on Password
    ... > that it's a web service so it's using soap stuff under neath. ... the service proxy inherits from SoapClient. ... the service interface inherits from SoapService. ... there is no secure way to use UsernameTokens. ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: WS Addressing
    ... > When I call the webservice, the FaultTo and ReplyTo-tags are in the Soap ... > Uri but he send it to the webserviceclient. ... Check the configuration file on the server for this web service (assuming this ... The web service is not obligated to honor the replyTo and faultTo from the ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
Loading