I have a classic ASP page that was implemented in 2002-ish. It was acting as an exposed entry point for a collection of SOAP web services.
All this page has is the VB script to create a SoapServer30 object, load a WSDL and WSML and send the object the HttpRequest in order to invoke the web service method.
The web service method is being specified in the HTTP Header's SOAPAction variable. The request also contains the SOAP envelope with the parameters for the web service call.
This process is no longer working due to changes in the WSDL, the deployment changes, etc. Basically it's too far gone and too much change has happened since 2002 to salvage this process.
We have a client though that does not want to make any code changes, they use Axis and Java to create the web service request and call this ASP page. I'd like to alter the VB script to simply pass the HttpRequest to an ASP.NET MVC page for parsing and to route to the correct web service. Then I'll simply return the resul开发者_运维问答t.
Any and all code samples would be greatly appreciated as I have little to no experience with VBScript. My experience is in C#.NET.
Thanks.
Why do you need VBScript at all any more? Why not simply create an ASP.NET MVC route that takes the request directly? I think the ASP.NET MVC route could simply have the same name as the old .asp file.
精彩评论