By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,983 Members | 1,627 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,983 IT Pros & Developers. It's quick & easy.

Does WSDL.exe's protocol parameter actually allow http post?

P: n/a
I have been asked to allow one of our old-school .asp pages to support
being used as a web service. Specifically, WSDL was mentioned. I am
not an expert on this , but I have done quite a bit of reading, and I
understand that I can create a WSDL file that supports HTTP POST and
then use WSDL.exe with the proper parameters to generate a web service
proxy. To this point, all I get from WSDL.exe when doing so is
"Warning: no classes were generated." I am using /protocol:HttpPost
and referencing the WSDL as a file url. This works if I run WSDL.exe
with the SOAP protocol. I have seen many, many references stating
that it should be able to work with an http post, but absolutely none
of them have worked for me, even when I copy/paste the exact code.

I have been researching and testing, testing and researching this for
days now. Hopefully someone can provide some answers or even a
completely new direction.

Please help!

Thanks.
-Thomas
Jan 14 '08 #1
Share this Question
Share on Google+
5 Replies


P: n/a
Thomas Lunsford <tl*******@gmail.comwrote in news:ba7e4816-12c1-46f8-
bf***************@k39g2000hsf.googlegroups.com:
I have been asked to allow one of our old-school .asp pages to support
being used as a web service.
Classic ASP doesn't support web services without additional components.

How are you turning your ASP page into a web service?
--
sp**********@rogers.com (Do not e-mail)
Jan 14 '08 #2

P: n/a

"Thomas Lunsford" <tl*******@gmail.comwrote in message
news:ba**********************************@k39g2000 hsf.googlegroups.com...
>I have been asked to allow one of our old-school .asp pages to support
being used as a web service. Specifically, WSDL was mentioned. I am
not an expert on this , but I have done quite a bit of reading, and I
understand that I can create a WSDL file that supports HTTP POST and
then use WSDL.exe with the proper parameters to generate a web service
proxy. To this point, all I get from WSDL.exe when doing so is
"Warning: no classes were generated." I am using /protocol:HttpPost
and referencing the WSDL as a file url. This works if I run WSDL.exe
with the SOAP protocol. I have seen many, many references stating
that it should be able to work with an http post, but absolutely none
of them have worked for me, even when I copy/paste the exact code.

I have been researching and testing, testing and researching this for
days now. Hopefully someone can provide some answers or even a
completely new direction.
I would suspect what is meant is that ASP Pages application functionality
would be converted/rewritten over to a .Net XML Web service solution. That
I know of, there is no way you're going to be able to take any classic ASP
page and do anything with it in .NET.

The WSDL would point to a url that was a .Net XML Web service solution to
generate the proxy classes in C# or VB .Net that a Web service client
application would use to access the Web Methods that the Web service
provides.

I think you first need to build a Web service application to understand what
is happening.

http://support.microsoft.com/default...;EN-US;Q301273

You can then build the proxy class off of the Http://Localhost/webservice to
see what is generated, which you can then include that class in a Web
service client project that would consume the Web service and use it.

Jan 14 '08 #3

P: n/a
On Jan 14, 4:45*pm, "Mr. Arnold" <MR. Arn...@Arnold.comwrote:
"Thomas Lunsford" <tlunsf...@gmail.comwrote in message

news:ba**********************************@k39g2000 hsf.googlegroups.com...
I have been asked to allow one of our old-school .asp pages to support
being used as a web service. *Specifically, WSDL was mentioned. *I am
not an expert on this , but I have done quite a bit of reading, and I
understand that I can create a WSDL file that supports HTTP POST and
then use WSDL.exe with the proper parameters to generate a web service
proxy. *To this point, all I get from WSDL.exe when doing so is
"Warning: no classes were generated." *I am using /protocol:HttpPost
and referencing the WSDL as a file url. *This works if I run WSDL.exe
with the SOAP protocol. *I have seen many, many references stating
that it should be able to work with an http post, but absolutely none
of them have worked for me, even when I copy/paste the exact code.
I have been researching and testing, testing and researching this for
days now. *Hopefully someone can provide some answers or even a
completely new direction.

I would suspect what is meant is that ASP Pages application functionality
would be converted/rewritten over to a .Net *XML Web service solution. That
I know of, there is no way you're going to be able to take any classic ASP
page and do anything with it in .NET.

The WSDL would point to a url that was a .Net XML Web service solution to
generate the proxy classes in C# or VB .Net that a Web service client
application would use to access the Web Methods that the Web service
provides.

I think you first need to build a Web service application to understand what
is happening.

http://support.microsoft.com/default...;Q301273&ID=KB....

You can then build the proxy class off of the Http://Localhost/webservice to
see what is generated, which you can then include that class in a Web
service client project that would consume the Web service and use it.
Thanks for the reply.

I have tried what you mention. The problem comes when I try to switch
from SOAP to HTTP POST. According to what I have read, if I use
wsdl.exe to create a web service proxy to use the http post protocol,
then communication will occur via form-variable name-value pairs just
as though I had posted from a html page (as opposed to via the SOAP
envelope).
Jan 14 '08 #4

P: n/a

"Thomas Lunsford" <tl*******@gmail.comwrote in message
news:c9**********************************@h11g2000 prf.googlegroups.com...
On Jan 14, 4:45 pm, "Mr. Arnold" <MR. Arn...@Arnold.comwrote:
"Thomas Lunsford" <tlunsf...@gmail.comwrote in message

news:ba**********************************@k39g2000 hsf.googlegroups.com...
I have been asked to allow one of our old-school .asp pages to support
being used as a web service. Specifically, WSDL was mentioned. I am
not an expert on this , but I have done quite a bit of reading, and I
understand that I can create a WSDL file that supports HTTP POST and
then use WSDL.exe with the proper parameters to generate a web service
proxy. To this point, all I get from WSDL.exe when doing so is
"Warning: no classes were generated." I am using /protocol:HttpPost
and referencing the WSDL as a file url. This works if I run WSDL.exe
with the SOAP protocol. I have seen many, many references stating
that it should be able to work with an http post, but absolutely none
of them have worked for me, even when I copy/paste the exact code.
I have been researching and testing, testing and researching this for
days now. Hopefully someone can provide some answers or even a
completely new direction.

I would suspect what is meant is that ASP Pages application functionality
would be converted/rewritten over to a .Net XML Web service solution. That
I know of, there is no way you're going to be able to take any classic ASP
page and do anything with it in .NET.

The WSDL would point to a url that was a .Net XML Web service solution to
generate the proxy classes in C# or VB .Net that a Web service client
application would use to access the Web Methods that the Web service
provides.

I think you first need to build a Web service application to understand
what
is happening.

http://support.microsoft.com/default...;Q301273&ID=KB...

You can then build the proxy class off of the Http://Localhost/webservice
to
see what is generated, which you can then include that class in a Web
service client project that would consume the Web service and use it.
Thanks for the reply.

I have tried what you mention. The problem comes when I try to switch
from SOAP to HTTP POST. According to what I have read, if I use
wsdl.exe to create a web service proxy to use the http post protocol,
then communication will occur via form-variable name-value pairs just
as though I had posted from a html page (as opposed to via the SOAP
envelope).

You go to a Web browser and in the address line enter http//url?wsdl. If it
doesn't come back with XML representing an XML Web Service, then I don't see
how you're going to generate any class using the .Net WSDL utility

Jan 14 '08 #5

P: n/a
Thomas Lunsford <tl*******@gmail.comwrote in news:c9af8e78-0f50-4ca8-
a5***************@h11g2000prf.googlegroups.com:
I have tried what you mention. The problem comes when I try to switch
from SOAP to HTTP POST. According to what I have read, if I use
wsdl.exe to create a web service proxy to use the http post protocol,
then communication will occur via form-variable name-value pairs just
as though I had posted from a html page (as opposed to via the SOAP
envelope).
It's not that simple - web services output specific XML, your classic ASP
page won't do it properly without additional components.

--
sp**********@rogers.com (Do not e-mail)
Jan 15 '08 #6

This discussion thread is closed

Replies have been disabled for this discussion.