Please support our Java advertiser: Lunarpages Java Web Hosting
Views: 1820 | Replies: 6
 |
•
•
Join Date: Jun 2004
Location: H4x0rville
Posts: 2,105
Reputation: 
Rep Power: 9
Solved Threads: 18
I've looked and looked for some good material on this exception, but I can't find anything helpful. I just don't understand it. It's suppose to be caught or thrown whenever a method is called when not suppose to be...But won't other exceptions be caught or thrown in it's place? If you have any comments or anything to say, please post!
•
•
Join Date: Dec 2004
Location: Singapore
Posts: 44
Reputation:
Rep Power: 4
Solved Threads: 1
Light Poster
but then u never catch this expection in the first place. if you want to catch all expections can try using this
try
{}
catch(Exception e)
{
} •
•
Join Date: Jun 2004
Location: H4x0rville
Posts: 2,105
Reputation:
Rep Power: 9
Solved Threads: 18
I know that, but I just don't undestand this exception. What is it for? I mean, when is a method called, but not suppose to be called?
•
•
Join Date: Nov 2004
Location: Netherlands
Posts: 5,752
Reputation:
Rep Power: 19
Solved Threads: 200
Think of calling a method to do a database query on a database that is closed.
Or calling a read method on a stream that's past the end of the data.
Or calling write methods on a readonly file.
Note that these won't throw IllegalStateException in Java but they could (they throw something more specific).
In general it's there to indicate you're trying to do something with an object that at that moment isn't possible to do with it.
Or calling a read method on a stream that's past the end of the data.
Or calling write methods on a readonly file.
Note that these won't throw IllegalStateException in Java but they could (they throw something more specific).
In general it's there to indicate you're trying to do something with an object that at that moment isn't possible to do with it.
As people are clearly allowed to attack me but I'm not allowed to defend myself, I no longer post to this site.
•
•
Join Date: Jun 2004
Location: H4x0rville
Posts: 2,105
Reputation:
Rep Power: 9
Solved Threads: 18
•
•
•
•
Originally Posted by jwenting
Note that these won't throw IllegalStateException in Java but they could (they throw something more specific).
This is what I was looking for. I was thinking this was the case,but wasn't sure. So I guess this means that this exception would have to be pretty high on the exception hierarchy?
•
•
Join Date: Nov 2004
Location: Netherlands
Posts: 5,752
Reputation:
Rep Power: 19
Solved Threads: 200
It is. But remember File et.al. typically throw IOExceptions which don't derive from IllegalStateException.
IllegalStateException is a RuntimeException, which is why you'll find few cases of it being explicitly caught (usually these are used to indicate programming errors rather than runtime problems, despite what their name suggests) while IOException is a regular Exception which requires catching at some point.
IllegalStateException is a RuntimeException, which is why you'll find few cases of it being explicitly caught (usually these are used to indicate programming errors rather than runtime problems, despite what their name suggests) while IOException is a regular Exception which requires catching at some point.
As people are clearly allowed to attack me but I'm not allowed to defend myself, I no longer post to this site.
•
•
Join Date: Jun 2004
Location: H4x0rville
Posts: 2,105
Reputation:
Rep Power: 9
Solved Threads: 18
So would it be called bad practice to throw one of these? I mean, couldn't it be almot considered as doing a catch-all-throw clause like throws Exception?
Have you ever seen this exception used before?
Have you ever seen this exception used before?
|
•
•
•
•
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
Linear Mode
