php, wsdl and asp.net

blackhorse

There is a wsdl url that is created on asp.net.

I can use soapUI, storm etc to connect to it. So the wsdl seems validated. I can open this wsdl in browsers. But when I try to submit this wsdl for online validation, the error says they cannot load the wsdl from the url I gave. And when I try to use

$c = new SoapClient('http://www.myclientssite.com/default.wsdl');

// I hide the site due to it is not for public.

I got the errors like

Fatal error: Uncaught SoapFault exception: [WSDL] SOAP-ERROR:
Parsing WSDL: Couldn't load from

What I knew is

1) It shouldn't be my php set up issue, I have been using php to access wsdl all the time, on different platforms too. They all works, except this one. I have tried this one on different server too, they all give the same error.

2) wsdl provider said it was built by asp.net, and other asp.net has no problems to access this wsdl and parse the data.

Are there any known issues with use php to access asp.net generated wsdl? (there is another wsdl by the same data provider on the same server, I have no problem with that wsdl.)

sneakyimp

I had a similar problem using WSO2's Web Services Framework for PHP. The problem was with how WSF/PHP was calculating a particular digest.

At any rate, my guess here is that SoapClient, because it is different than the ASP.net SOAP library, is not parsing the WSDL successfully. You may need to specify more options when you create your soa client. Perhaps try something like this:

<?php


try
{
  $c = new SoapClient("http://www.myclientssite.com/default.wsdl", array(
  "trace" => 1,
  "exceptions" => 0));
} catch (Exception $e) {
  echo 'EXCEPTION!';
  var_dump($e);
}
?>

You may or may not get a better idea of what is failing. Note that SoapClient's constructor permits a large variety of options. You may need to set some:
http://us.php.net/manual/en/soapclient.soapclient.php

It may be that the default configuration of SoapClient--when no options are specified--is not compatible with the server's WSDL.

You could also try a different WSDL client solution -- like WSF/PHP. Version 2 is out. Who knows, it may just work.

EDIT: corrected bug in code.

blackhorse

thanks!

I fixed my problem.

My guess is that the wsdl was not sending the content length in the header. someone suggested that soapclient used http 1.1 so it required content length. I am not sure if this is the case but i just loaded the wsdl locally. It fixed the problem.

sneakyimp

Could you elaborate?

Do you mean to say that the ASP.NET hosted WSDL page, although hosted on a web server using http, did not send a content-length header and that was the problem?

If so, we might be able to recommend a fix to the folks developing SoapClient. This could solve the problem for many people.

blackhorse

I don't think it is necessary that asp.net did that. But I saw some other posts suggested the problem could be like missing content length, using nusoap (http1.0) instead soapclient (http1.1) would make it work etc. Or load the wsdl locally instead. I didn't dig into it too much.

I loaded it locally, it worked.

I also used browser to get the wsdl, saved it as static xml page, and used this new static xml's url to replace the original wsdl url. It works too.

So I think at least this could be some solutions for some cases.

If we can view it in browser as valid xml, then load it locally or maybe sometimes save it as an xml and load this one through http may work.

blackhorse

Or this thread gives another reason (or actually it is the same reason?) why asp.net wsdl sometimes works for http 1.0 not http 1.1.

http://forums.asp.net/t/1465929.aspx

I don't know why my approach, use browser get the wsdl and save it as xml and load this static xml page works. (this is even easier than load locally. Load locally I need to change some codes, but this way, I only need to load from another url and everything is working) Maybe you guys can dig out the root of the reasons and fixes.

Thanks.