Why aren't these throw statements giving me a compiler error?

Question

public String runQuery(String q) throws JsonGenerationException, JsonMappingException   
 {   
    Graph g = null;
            try {
                g = jdbcTemplate.query(q, new Neo4jGraphResultSetExtractor());
            } catch (DataAccessException e) {

                if (e instanceof UncategorizedSQLException)
                    {
                    //Invalid cypher query
                    throw (UncategorizedSQLException)e;
                    }

                else throw e; 
            }

    json = g.toJson(); //throws JsonGenerationException, JsonMappingException
    return json;
}

Shouldn't the compiler require that this method also throws UncategorizedSQLException, DataAccessException?

Not if they extend from RuntimeException, which seems to be the case. — pedromss, Jun 30 '15 at 21:40
@pedromss Huh - They do. Why shouldn't run time exceptions throw compiler errors? Could you post it as an answer? — dwjohnston, Jun 30 '15 at 21:41
http://stackoverflow.com/questions/6115896/java-checked-vs-unchecked-exception-explanation — Jan Groth, Jun 30 '15 at 21:42

score 0 · Answer 1 · edited May 23 '17 at 10:24

0

Because they are runtime exceptions, which are unchecked meaning that the compiler does not require explicit catching of them.

See this question for more details.

edited May 23 '17 at 10:24

Community

1
1

answered Jul 20 '15 at 23:42

dwjohnston

11,163
32
99
194

Why aren't these throw statements giving me a compiler error?

1 Answers1