Any reason why? NPE's are not useful to the end user.
Ceki G�lc� wrote:
May I ask you to defer this discussion to later?
At 09:45 PM 12/1/2004, Paul Smith wrote:
Can we at the VERY least NOT let the user try to decipher a NullPonterException.
Isn't there some way we can detect this situation (since we clearly know that it can happen from this discussion), and then throw some sort of more informative Exception (my vote would be IllegalStateException) with some detailed message giving those users who perhaps stepped onto the cluetrain illegally (maybe they didn't pay?) a bit of a helping hand.
If Kermit the Frog (running out of proverbial users I think) saw a NPE, he'd immediately associate that with a bug in log4j code (even though he's wrong). Lets be a bit more open about it.
cheers,
Paul Smith
--
*Paul Smith *Software Architect
*Aconex * 31 Drummond Street, Carlton, VIC 3053, Australia *Tel: +61 3 9661 0200 *Fax: +61 3 9654 9946 Email: [EMAIL PROTECTED] www.aconex.com**
This email and any attachments are intended solely for the addressee. The contents may be privileged, confidential and/or subject to copyright or other applicable law. No confidentiality or privilege is lost by an erroneous transmission. If you have received this e-mail in error, please let us know by reply e-mail and delete or destroy this mail and all copies. If you are not the intended recipient of this message you must not disseminate, copy or take any action in reliance on it. The sender takes no responsibility for the effect of this message upon the recipient's computer system.**
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
