Re: Ws-Addressing - WSE and vanilla Web Service Proxies

Gracias Pablo.

The pipeline process is something i'm reasoable familiar with - didn't
realise there was such a significant difference in the generated proxies.

Here is crux of my problem - i need to allow a normal .Net service to use
the routing services i am creating - that is *essential* and some may not use
WSE.

Got any pointers on making this work?

saludos,
steven.
http://stevenR2.com

"Pablo Cibraro" wrote:

Hi Steven,

The proxies created by WSE are completely different to those created by
..NET.
The WSE proxies intercept the SOAP messages and execute a pipeline where the
message is transformed to a different version (The new message version
contains WS-Addressing and WS-Security headers).
The WS-Addressing headers are always added in that pipeline, but the
WS-Security headers are not (that depend on some WSE specific configuration,
the WSE policies).

The same happens on the server side, if you configure WSE, a WSE pipeline
will run before calling to your service (This pipeline performs different
security validations and removes the WS-Addressing and WS-Security headers).

The best way to know what headers are required is to enable WSE tracing and
see the different messages between the client and the service.

Regards,
Pablo Cibraro
http://weblogs.asp.net/cibrax
[MVP - Connected Systems Developer]


"Steven L" <Steven L@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CEC76416-7CEC-464F-950C-A502B33EF494@xxxxxxxxxxxxxxxx
I have a hub performing some internal routing for a set of services we
have,
using the WS-Addressing support in WSE 3.0.

When a vanilla .Net generated proxy client tries to call the service you
get:
"Microsoft.Web.Services3.Addressing.AddressingFault: Message Information
Header Required"

When a WSE generated proxy client does the same it works fine.

Can someone explain or point me at the different in the client proxy
configurations between these.

I will have some vanilla .Net clients and some Java clients and so i need
to
tell them exactly what (Soap Headers?) to set on their proxy client so
they
can successfully call the routing service - i don't need to set these when
calling the service directly, so any detail on exactly what causes this
requirement by the WSE would be greatly appreciated!

Regards,
Steven
http://stevenR2.com



.

Relevant Pages

  • Re: Ws-Addressing - WSE and vanilla Web Service Proxies
    ... I can clearly get this working by figuring out when i have a WSE client ... writing services on the assumption that my decision to use routing is a good ... You will need minimally the wsa headers. ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Ws-Addressing - WSE and vanilla Web Service Proxies
    ... Header Required" when i call the routing service from a non-WSE client proxy. ... I actually implemented exactly as stated in the WSE patterns book ... ... contains WS-Addressing and WS-Security headers). ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Ws-Addressing - WSE and vanilla Web Service Proxies
    ... the proxies inherits differently from vanilla ... asp.net web services and those proxies injects headers into the messages ... Header Required" when i call the routing service from a non-WSE client ... I actually implemented exactly as stated in the WSE patterns book ... ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Ws-Addressing - WSE and vanilla Web Service Proxies
    ... the routing service is It. ... In WSE 2.0, it is ... I can't use this in the nonWSE client ... You will need minimally the wsa headers. ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Ws-Addressing - WSE and vanilla Web Service Proxies
    ... The WSE proxies intercept the SOAP messages and execute a pipeline where the ... The WS-Addressing headers are always added in that pipeline, ... When a vanilla .Net generated proxy client tries to call the service you ...
    (microsoft.public.dotnet.framework.webservices.enhancements)