Java程序中自带catch,如何避免在java中尝试catch块

I'm very new to java and the idea of try catch blocks to handle exceptions.

This roughly what I'm ending up with, and there simply has to be a better way:

try {

JSONObject jsonObject = new JSONObject(jsonString);

int aCount = jsonObject.getInt("acount");

String devTok = jsonObject.getString("dt");

String qURL = jsonObject.getString("qu");

try {

DatastoreService datastore = DatastoreServiceFactory.getDatastoreService();

Key qKey = KeyFactory.createKey("qu", qURL);

int dsACount = (Integer) datastore.get(qKey).getProperty(kLastKnownANumber);

//..etc.. more try catch blocks needed

} catch (EntityNotFoundException e) {

e.printStackTrace();

}

} catch (com.google.appengine.repackaged.org.json.JSONException e) {

e.printStackTrace();

}

There are more try catch blocks embedded in the same way, so that at the end, there is just a lump of catch blocks. How else should exceptions be handled, Eclipse keeps asking my to either surround with a try catch block or "Add throws declaration".

Sometimes I want to catch certain exceptions, for example if it can't find an entity, I want to print something like "Entity not found", and if the JSON string can't be parsed into an object, I want to print something like "Can't parse JSON".

(I'm used to objective-c where the are delegate methods for failure, or the method returns null and you have passed a pointer to [a pointer to] an NSError object, which will have been "filled", Is there somewhere to learn about try-catch?)

解决方案

If all you're doing is catching them and printing the stack trace regardless of the exception type, you can just wrap the code in one large try/catch block. To save many "catches", you can catch java.lang.Throwable which is the interface that all exceptions implement. If not, you can have a catch for every type of checked exception the code you're calling throws, and handle them specifically.

Eclipse keeps asking you to do so because Java code will not compile if the checked exceptions are not caught, or declared to be thrown by the caller.

+Adding this comment to the answer (Thanks, Paul Tomblin):

In production quality apps you'd be logging the trace, adding some logic where you're handling the exception in a right way, taking an alternate flow, and/or re-wrapping it in another exception and throwing it, etc. It all depends on the particular problem you're trying to solve.