12408
Reporter: kbraak
Assignee: mdoering
Type: Bug
Summary: checklistbank-ws: dataset_metrics returns UniformInterfaceException
Priority: Critical
Resolution: Fixed
Status: Closed
Created: 2012-11-26 11:27:14.297
Updated: 2013-12-09 14:01:27.087
Resolved: 2012-11-27 13:59:54.046
Description: In the Portal Dataset SearchAction, there is a call to
http://staging.gbif.org:8080/checklistbank-ws/dataset_metrics/
to retrieve metrics for each checklist returned.
While retrieving the metrics for this particular checklist (479cef35-00e0-440b-aee5-4850f1e560a3), an unexpected UniformInterfaceException was being caught.
This problem was fixed in http://code.google.com/p/gbif-portal/source/detail?r=1178
But, there should never be any UniformInterfaceException thrown by the WS. All unmapped exceptions should be converted into a ServiceUnavailableException.
Further information:
A reference guide of our Service Exceptions exists here: http://dev.gbif.org/wiki/display/POR/Service+Exceptions]]>
Author: mdoering@gbif.org
Created: 2012-11-27 11:29:14.99
Updated: 2012-11-27 11:35:04.334
http://staging.gbif.org:8080/checklistbank-ws/dataset_metrics/479cef35-00e0-440b-aee5-4850f1e560a3 returns a 204 no content right now - that is definitely wrong.
Considering to open a new gbif common issue to convert a 204 into a ServiceUnavailableException. Or return null instead?
Author: mdoering@gbif.org
Comment: The NullToNotFoundInterceptor is somehow not bound - this should have converted the null into a 404. Without it null becomes no content 204
Created: 2012-11-27 13:01:38.64
Updated: 2012-11-27 13:01:38.64
Author: mdoering@gbif.org
Created: 2012-11-27 13:55:59.868
Updated: 2012-11-27 13:55:59.868
a common problem: http://dev.gbif.org/issues/browse/GBIFCOM-106
We can bypass this for now by converting all 204 no content responses into a null content - seems like a fair and safe addition in any way.