feature request #2711
Proper handling of cdm webservice HTTP status codes
Currently the HTTP status codes returned by the cdm web-service are neglected. For example a call to http://220.127.116.11:8080/cichorieae/portal/taxon/37d81a19-8d8c-44e8-8140-a6d2aaab4149/synonymy causes an HTTP ERROR 500. The resulting json object returned by the
cdm_ws_get() function is null but the user is not informed about the error that occurred. The synonymy page of Askellia benthamii ( http://wp6-cichorieae.e-taxonomy.eu/portal/?q=cdm_dataportal/taxon/37d81a19-8d8c-44e8-8140-a6d2aaab4149/synonymy ) is almost empty.
We need to find a way to handle these errors properly, that is to inform the user on such problems. But keep in mind that it might be necessary to ignore HTTP errors in some cases, that is to suppress warning messages.
related tickets which could have benefited from better http status handling.
consider to display notifications in the according web page part to notify the user that this part has problems.
- #4972 (cyprus: mixed vocabularies break custom status colors)
#2 Updated by Andreas Kohlbecker about 4 years ago
- Target version changed from cdm_dataportal - Next Major Release to DataPortal - Reviewed Next Major Release
- Priority changed from Highest to Priority13
see also [#4977#note-4]
in case of errors in the search web service the result says "No matching entries found". It should better say that an exception occurred if possible.