Talk:Errors handling in web services: Difference between revisions
From MoodleDocs
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
* the difference between message/debuginfo is that message can be considered as a code error (e.g. "A search criteria is wrong"). Debuginfo contains the detailled reason why it failed (e.g. "You are not allowed to search on the theme field"). | * the difference between message/debuginfo is that message can be considered as a code error (e.g. "A search criteria is wrong"). Debuginfo contains the detailled reason why it failed (e.g. "You are not allowed to search on the theme field"). | ||
* sometimes exceptions are thrown at lower level and they are already translated. | * sometimes exceptions are thrown at lower level and they are already translated. | ||
* we can not change much of the existing thrown web service exception without potentially breaking existing clients. | * we can not change much of the existing thrown web service exception without potentially breaking existing clients. However we can make the next functions consistent :) | ||
Revision as of 04:27, 8 May 2012
Jerome Mouneyrac - 08/05/2012
About the exception format (https://docs.moodle.org/dev/Errors_handling_in_web_services#How_to_handle_exception_on_the_client_side):
- the difference between message/debuginfo is that message can be considered as a code error (e.g. "A search criteria is wrong"). Debuginfo contains the detailled reason why it failed (e.g. "You are not allowed to search on the theme field").
- sometimes exceptions are thrown at lower level and they are already translated.
- we can not change much of the existing thrown web service exception without potentially breaking existing clients. However we can make the next functions consistent :)
