WebService port usage

[Jeff Hamilton]

Thanks, Chris. That does work when developing a .Net client, however I
forgot to mention that I am calling the web service from a html page using
javascript and am building a Flash component that will call the service
also. I figure I can generate the wsdl on the server and then copy it to a
static file, changing the port numbers in the <port> element. Then I can
reference that wsdl file from the clients. Would this be the easiest way to
work around this problem?

Jeff,

When you generate the web service proxy, the Add Web Reference wizard
embeds the service location in the proxy code. You can change the proxy
code to pull the service location from a config file by right clicking
or your web reference under the web references folder in the Solution
Explorer view. Select properties and set URL Behavior to Dynamic. Now
you can configure the location of your Web Service in the config file.

HTH,
Christoph Schittko
MVP XML

-----Original Message-----
From: Jeff Hamilton [mailto:[email protected]]
Posted At: Monday, September 20, 2004 2:05 PM
Posted To: microsoft.public.dotnet.framework.aspnet.webservices
Conversation: web service methods being called using incorrect port
Subject: web service methods being called using incorrect port

I am developing a web service which will be hosted on a machine running
ISA
Server 2000. ISA is using port 80 and IIS is using port 81. When using a
client app to test the web service I am successfully connecting to the
WSDL
using port 80, however when I call a method it is sending the request to
port
81. I examined the WSDL file and at the end there are <port> tags which
specify the location as using port 81. How can I configure the service to
use
port 80 so the request goes through ISA Server?

Expand AllCollapse All


Manage Your Profile |Legal |Contact Us |MSDN Flash Newsletter