Tonight, we re-released version 2.0 of the Hoover's API to Development. This re-release was done to put in a work-around for a known Axis2 bug that we discovered this weekend. Apparently, Axis2 does not handle multiple concurrent calls to retrieve the WSDL. In fact, if you review the Jira details (http://issues.apache.org/jira/browse/AXIS2-3276), this bug has been open for over a year, so we have little hope that it will be fixed soon. Therefore, we removed the WSDL from the Axis Archive and have placed it under its own directory that is not served up by Axis2. This will remove the concurrency bug, BUT it does mean that you cannot add "?wsdl" to the endpoint and get the WSDL. We weighed the options, and felt that this would be the best solution given our timeline and constraints.
Go to http://hapi-dev.hoovers.com/axis2/HooversAPI-20/Hapi.wsdl for the 2.0 WSDL.
If you are a Java developer, please be careful with your use of Axis2, as the generated client code is also not thread safe and you could see concurrency issues in your code if not careful.
Thanks. Let us know if you have any comments about this.
Tonight, we re-released version 2.0 of the Hoover's API to Development. This re-release was done to put in a work-around for a known Axis2 bug that we discovered this weekend. Apparently, Axis2 does not handle multiple concurrent calls to retrieve the WSDL. In fact, if you review the Jira details (http://issues.apache.org/jira/browse/AXIS2-3276), this bug has been open for over a year, so we have little hope that it will be fixed soon. Therefore, we removed the WSDL from the Axis Archive and have placed it under its own directory that is not served up by Axis2. This will remove the concurrency bug, BUT it does mean that you cannot add "?wsdl" to the endpoint and get the WSDL. We weighed the options, and felt that this would be the best solution given our timeline and constraints.
Go to http://hapi-dev.hoovers.com/axis2/HooversAPI-20/Hapi.wsdl for the 2.0 WSDL.
If you are a Java developer, please be careful with your use of Axis2, as the generated client code is also not thread safe and you could see concurrency issues in your code if not careful.
Thanks. Let us know if you have any comments about this.
Tags