BUG in Microsoft.Web.Services2.WebServicesClientProtocol WSE 2.0 S

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Thomas S. Trias - 01 Mar 2005 17:57 GMT

If you specify a Destination with both an Address and a Via, the Address is
used as both the Url property (transport) AND the "To" SOAP header. The Via
portion is effectively ignored, making it impossible to connect to web
services with SoapActor attributes or behind NAT / PAT.

I can provide a complete test case upon request, although the issue is quie
easy to replicate.

Thanks,

Thomas S. Trias
Senior Developer
Afni Insurance Services
http://www.afniinc.com/

Reply to this Message

Thomas S. Trias - 01 Mar 2005 17:59 GMT

FYI WSE 2.0 SP2

Reply to this Message

Dilip Krishnan - 02 Mar 2005 03:25 GMT

Hello Thomas,
You would need to set the Via in the request soap context theres tons
of examples [0] of people having it working

[0] - http://www.softwaremaker.net/blog/PermaLink,guid,78f77920-5a90-42bf-a9a7-a4bf0dc
f9215.aspx

HTH
Regards,
Dilip Krishnan
MCAD, MCSD.net
dkrishnan at geniant dot com
http://www.geniant.com

> If you specify a Destination with both an Address and a Via, the
> Address is used as both the Url property (transport) AND the "To" SOAP
[quoted text clipped - 11 lines]
> Afni Insurance Services
> http://www.afniinc.com/

Reply to this Message

Thomas S. Trias - 02 Mar 2005 15:35 GMT

Is this behavior by design? What is the purpose of the Destination property
on the WebServicesClientProtocol class, if not to set the WS-Addressing
information and transport?

Also, most of the addressing samples I've seen use soap.tcp based services,
and don't have concrete examples of proxies based upon
Microsoft.Web.Services2.WebServicesClientProtocol.

Thomas S. Trias
Senior Developer
Afni Insurance Services
http://www.afniinc.com/

> Hello Thomas,
> You would need to set the Via in the request soap context theres tons
[quoted text clipped - 24 lines]
> > Afni Insurance Services
> > http://www.afniinc.com/

Reply to this Message

Thomas S. Trias - 02 Mar 2005 16:25 GMT

Actually, the Destination property does work. I am an idiot, and I am not
ashamed to admit it.

I had setup the service to use an SCT:

Dim oClient As SecurityContextTokenServiceClient = _
New SecurityContextTokenServiceClient(New EndpointReference(New
Uri(MyBase.URL)))

I changed this to:

Dim oClient As SecurityContextTokenServiceClient = _
New SecurityContextTokenServiceClient(MyBase.Destination)

And now everything works fine.

Sorry for letting my frustration get the better of me.

Thomas S. Trias
Senior Developer
Afni Insurance Services
http://www.afniinc.com/

Reply to this Message

BUG in Microsoft.Web.Services2.WebServicesClientProtocol WSE 2.0 S

Free Magazines