Certainly a preference (and possibly desired to be localized), but I like to be detailed and offer a way around the problem or a possible cause.
/snark-asm/ Or, if you're done acquiring Yahoo, you could politely throw an exception 41850, which could easily be cross referenced in the user handbook.
Bill Shirley - bshirley - frazerbilt.com
if (Posts < 30) you.read( JavaRanchFAQ);
Joined: Mar 28, 2006
Then after the client side catches "CustomerException", is it going to really check the e.getMessage() to see what's the message ? I thought usually when client gets the "CustomerException" it just does something mechanically. If you put rich and detailed information into the Exception constructor, does it mean you want client to check this messge and do different things according to the different messages ? If that;s the case, are you going to hard-coded the client code like
if (e.getMessage().equals("This is a database error") // go to databse error page if(e.getMessage().equals("This is a input error") // go to input error page ...
This sounds crazy.. Maybe my understanding is wrong. Please tell me how client can really use the "messge" embedded in the exception constructor.
It has been my experience that most people do not want all the information I tend to give. I suggest putting up an explaination on the console that most people could interpret as something wint arrrohng.
Put things like jump table indexes or technical trace-log messages in a log file so the tech that is trying to fix it can inform supervisor where the problem is. Don't let exception catching become bulky, but put something there that can be used to trace the matter.
"The differential equations that describe dynamic interactions of power generators are similar to that of the gravitational interplay among celestial bodies, which is chaotic in nature."