We seem to be experiencing the same problem. In our case, it is both the
SoapClient and the SoapServer class which fail to load wsdl files (with
the same error message as above), regardless of where the files are
located on our server. I found a workaround which is allowing the wsdl
files to be loaded, but which may be causing unwanted changes in how our
SOAP objects are delivered.
I changed:
$server = new SoapServer('/path/to/wsfile.wsdl');
to:
$server = new SoapServer(null, array('uri' => '/path/to/wsfile.wsdl'));
For the SoapClient code, I changed:
$client = new SoapClient('https://domain/path/to/wsfile.wsdl');
to:
$client = new SoapClient(null, array('uri' =>
'https://domain/path/to/wsfile.wsdl', location =>
'https://domain/path/to/wsfile.wsdl'));
This got our client code tests to successfully return SOAP objects, but one of
our customers using existing client side code (which has not been changed) has
been experiencing errors when attempting to parse the objects they are
receiving.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1160336
Title:
SOAP Client failed to load entry
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1160336/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
