Ask a Question related to ASP.NET Web Services, Design and Development.
-
Ray Johnson #1
How do I override the soap:address field in the auto-generated WSDL document?
My web service will be served on a farm of servers. However, the WSDL
document that get's created
uses information about the local machine. More specifically the
"soap:address" field is set to something
like this:
<soap:address location=http://webserver1:7000/ingenio.asmx />
However, for people to use the real service they need to hit a different
address on our
load balancer. So the soap:address really should be something like this:
<soap:address location=http://services.ingenio.com/ingenio.asmx />
I have been unable to figure out how to tell the .asmx page to generate a
different WSDL
file with the proper address. ANyone know how to do this?
Ray
Ray Johnson Guest
-
Making a value-type property optional in WSDL generated by ASP.NET
Hello all, Is there a way to mark a value-type property on a class as optional when being used as a parameter to a web service? The problem is... -
Array Of Arrays - Cape Generated WSDL with .NET
Hello all, I have a CAPE generated WSDL that is an array of arrays. Let me elaborate I have a struct of public class Properties() { } Now I... -
.NET should move documentation from the WSDL to the generated code
When I have a WSDL that is documented like: <?xml version="1.0" encoding="UTF-8"?> <!-- edited by Sebastien Tardif (Anacomp) --> <wsdl:definitions... -
wsdl.exe fails with WebMethods generated wsdl file
Using WebMethods, Inc Developer tool to create a wsdl for a flow service. Try to use .NET wsdl utility to create a C# proxy, but get the errors... -
Problem generating appropriate WSDL from C# classes generated from an XSD
Hi all, We are integrating Great Plains 7.5 (GP) with BizTalk 2004 (BT) through web services. GP's connectivity component (eConnect) works... -
Jan Tielens #2
Re: How do I override the soap:address field in the auto-generated WSDL document?
Check out following article:
[url]http://msdn.microsoft.com/webservices/default.aspx?pull=/library/en-us/dnweb[/url]
srv/html/insidewsdl.asp#insidewsdl_code15
Inside WSDL with .NET Attribution
Code block 15 depicts the service element for the MyStore Web service. The
port element is actually a sub-element located under the Service element.
(The Service element will be discussed in the next section.) The port is
given a unique name within the Service element, which in this case is
MyStoreSoap and is linked to a previously defined binding, also named
MyStoreSoap, via the binding attribute. Finally and most importantly, the
port element contains a SOAP address element that specifies the physical
address of this port. If you are using the HTTP transport, then this address
is a URL. If the transport specified in the Bindings element is SMTP, then
this address would be an e-mail address. All requests transmitted to this
address must use the transport and protocol specified in the MyStoreSoap
binding element.
--
Greetz
Jan Tielens
________________________________
Read my weblog: [url]http://weblogs.asp.net/jan[/url]
"Ray Johnson" <rayj@ingenio.com> wrote in message
news:e6NHCCY2DHA.2428@tk2msftngp13.phx.gbl...>
> My web service will be served on a farm of servers. However, the WSDL
> document that get's created
> uses information about the local machine. More specifically the
> "soap:address" field is set to something
> like this:
>
> <soap:address location=http://webserver1:7000/ingenio.asmx />
>
> However, for people to use the real service they need to hit a different
> address on our
> load balancer. So the soap:address really should be something like this:
>
> <soap:address location=http://services.ingenio.com/ingenio.asmx />
>
> I have been unable to figure out how to tell the .asmx page to generate a
> different WSDL
> file with the proper address. ANyone know how to do this?
>
> Ray
>
>
Jan Tielens Guest



Reply With Quote

