Can a exception be diasabled? in eclipse

Question

I am finding an exception extremely difficult to cope with,
ArrayIndexOutOf bounds
No matter what I do, when I try to access the array, I am getting an error.
Is there an way to over come this exception checking all together?
I tried to create my own exception but even that is stopping the execution of the code and coming to the catch block. I want my code to run in spite of an exception.
I am using eclipse, and seems to have a way disable the exception or to increase the hitcount, even if I disabled or if I put the hitcount to some large integer too, I am getting exception.
Some one please help me.

Answer 1

I agree with georgemc: exceptions are used to indicate that an exceptional circumstance occurred, a situation where the assumptions of the regular program flow don't hold. They can't be disabled and shouldn't be ignored.
In this particular case, you are trying to access an element of an array that does not exist, meaning either your assumptions about the length of the array are wrong, or your assumption about the legality of the index value you use to access the array is. Remember that arrays are fixed in length, and that their indexes run from 0 to the length of the array minus 1. An empty array doesn't have any valid indexes.
It is your responsibility to make sure you access an array in a legal way, meaning you will either need to create programmatic checks to test your assumptions and respond accordingly, or reevaluate your assumptions until you find the correct ones.
For example, if you assume that the array you are dealing with will always have at least a length of 5, so you can safely access array[4], you need to decide what to do if this assumption fails for some reason. What should happen if the array is not length 5? What should happen if the array is null? You could create a check in your code that checks the length of the array before you use it. If the length of the array is less than 5, you could just ignore it and go on with the rest of the program/method. Or you could throw an IllegalArgumentException if the array is a method parameter called by code outside your control. Or you could fix the code that sets/creates the array. In any case, you have to do something.