SOAP Errors
2012-11-28 07:33:38.786613+01 by meuon 0 comments
If you are going to force me to use your SOAP XML server, your API should not dump stack traces, it should give me a nicely formatted SOAP with some error condition/code/description. Yes, I am delusional and have added "is_soap_fault()" code so I can deal with such insanity.
Should a consumer of a production web service be exposed to the internal issues and configurations of your system. Should I know that the code is in c:\\webapp\.... and see the whole cascading gibberish dump or should I simply get the error: "Something bad happened, please contact XYZ with error code 9999".
But my real question is: If the initial error is "Can not connect to the database server", why did your application attempt multiple functions after that break?