Flutterby™! : SOAP Errors 2012-11-28 07:33:38.786613+01

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?

Comment policy

We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.

Flutterby™ is a trademark claimed by