dotnet web services: I have a friend that used a program called CICS2WS that created a WSDL to
allow our PC programs to retrieve mainframe data. In the WSDL that was
created, the <address location> tag only contains the URL for where the
service is located

<wsdlsoap:address location="http://mydomain.com/services" />

However it also contains the tag
<wsdl:service name="MstrGet">

However trying to access the web service via
http://mydomain.com/services/MstrGet.asmx yields a Server error. Besides,
there is no indication that the program that generated the WSDL also
generated an asmx file. Can the actual WS file be determined without have
..asmx?


Does a web service have to have an asmx extension OR can it be a generic one
like .ABC? OR, does an extension have to be specified at all????. The URL is
the WSDL (as the web browser sees it) is just another sub directory. Ill
admit I’m not well versed in mainframe programming, but I’m trying to figure
out from the WSDL that got generated what the actual service to call from the
browser is. I’ve only ever seen something.ASMX. I don’t see how the browser
is supposed to know of a service without an file extension.

--
JP

=?Utf-8?B?SlA=?= <JP@discussions.microsoft.com> wrote in
news:714CF83E-3B04-46AE-91A5-C9F557B9CD0F@microsoft.com:

[quoted text, click to view]

Browsers determine content through MIME headers rather than file
extensions.

Is the web service a .NET web service? The programmer may have created a
HTTP handler that does some URL mapping. It's rather straightforward to do,
but I'm not sure if it buys you very much. Maybe the programmer thought it
looks slicker...



--