Since my last post I found this bug which has been open since 2001.
Its the comment from webrejin which I liked... "why does a FileNotFoundException not tell which file was not found?"
If you can think of any others let me know, or add them to that bug, or just vote for it.
Layers and Gateways, a historical view
-
One of the major issues in building the Internet or any large network is
internetworking. If you have two networks built and run by different
entities, h...
3 days ago
Comments:
I'll agree with ClassCastException (or InvalidCastException for us C# people)
It'd be quite nice to get
InvalidCastException "TcpSocket cannot be cast as string" type thing.
But the FileNotFound *shouldn't* tell you where it was looking,
- imagine in a web environment if people saw the file structures of your server through the error messages. - I reckon it raises security problems
"imagine in a web environment if people saw the file structures of your server through the error messages"
I think you'd be making a mistake if you let the internal error messages end up on the screen.
You should use simple error codes to allow your users to report errors, and keep sensitive information safe in the error log.
blog comments powered by Disqus