http://hapi-dev.hoovers.com/axis2/services/HooversAPI-20?wsdl reports that a WSDL cannot be generated for this service. The service itself is returning a SOAP fault.
To be clear, the endpoint has not changed. The WSDL was removed from the archive due to an Axis2 bug. Please see this post (http://developer.hoovers.com/forum/read/48297) and the documentation that Brian listed.
However, I am curious why you still need the WSDL? Are you grabbing the WSDL often or was last night the first time you tried to go get it for version 2.0? You really only need to get the WSDL once to create your code, and then you should not need it after that point.
Point taken Elliot. I have now downloaded a local copy of the wsdl to support my code.
I am using the PHP SoapClient class to consume the HAPI service. This class is instantiated using a WSDL and generates the code stubs on the fly to be able to make calls to the available endpoints. So technically, there are no static functions in my code base that correspond to the HAPI endpoints. I suppose it reduces the need for additional lines of code and makes development a bit faster when I can focus in on just those endpoints that are relevant to my app.
Good to know! Thank you for the explanation, as I am not a PHP developer. What you say makes sense and explains why it is grabbing the WSDL every time. Pulling it local sounds like a good work-around, as the WSDL will not change for a given version. When we need to make changes to the WSDL, we increment the version number, so you should be safe.
Is there not a way to tell the SoapClient to cache the WSDL in memory?
Hello!
http://hapi-dev.hoovers.com/axis2/services/HooversAPI-20?wsdl reports that a WSDL cannot be generated for this service. The service itself is returning a SOAP fault.
Has the endpoint changed?
Thanks!
SR
bhawley – 9 months ago
Hi Shaheeb,
Yes, it has changed due to a bug in Axis2. The WSDL for the Hoover's API can be found at http://hapi-dev.hoovers.com/axis2/HooversAPI-20/Hapi.wsdl
This is documented at http://developer.hoovers.com/page/docs
Thanks,
Brian
Elliot – 9 months ago
To be clear, the endpoint has not changed. The WSDL was removed from the archive due to an Axis2 bug. Please see this post (http://developer.hoovers.com/forum/read/48297) and the documentation that Brian listed.
However, I am curious why you still need the WSDL? Are you grabbing the WSDL often or was last night the first time you tried to go get it for version 2.0? You really only need to get the WSDL once to create your code, and then you should not need it after that point.
Thanks.
Shaheeb Roshan – 9 months ago
Point taken Elliot. I have now downloaded a local copy of the wsdl to support my code.
I am using the PHP SoapClient class to consume the HAPI service. This class is instantiated using a WSDL and generates the code stubs on the fly to be able to make calls to the available endpoints. So technically, there are no static functions in my code base that correspond to the HAPI endpoints. I suppose it reduces the need for additional lines of code and makes development a bit faster when I can focus in on just those endpoints that are relevant to my app.
Thanks folks!
SR
Elliot – 9 months ago
Good to know! Thank you for the explanation, as I am not a PHP developer. What you say makes sense and explains why it is grabbing the WSDL every time. Pulling it local sounds like a good work-around, as the WSDL will not change for a given version. When we need to make changes to the WSDL, we increment the version number, so you should be safe.
Is there not a way to tell the SoapClient to cache the WSDL in memory?
Thanks again.
Elliot