Throws and throw in same method

Question

I have a method:

public List<Model> getModelList() throws ModelNotFoundException {
    if (modelList.isEmpty()) {
        throw new ModelNotFoundException("Model list is empty!");
    }
    return modelList;
}

Is it redundant to use throws with throw? If I remove throws ModelNotFoundException, idea underlines throw new ...

That's how checked exceptions are implemented – Ryuzaki L Nov 17 '19 at 18:43 — Ryuzaki L, Nov 17 '19 at 18:43

score 0 · Accepted Answer · answered Nov 17 '19 at 18:58

As per your question

Is it redundant to use throws with throw?

No. It is perfectly valid.

Besides if ModelNotFoundException is an unchecked exception like NullPointerException, it is not required to declare with throws clause in the method.

if ModelNotFoundException is a checked exception like FileNotFoundException, it is similar to your code. It means you have to declare it with throws and also use throw based upon condition.

You may get answers from seniors also about it.

score 0 · Answer 2 · answered Nov 17 '19 at 18:59

0

Seems like ModelNotFoundException is checked exception, therefore you should indicate that the method throws that. If you change it to unchecked exception, it will compile.

Understanding checked vs unchecked exceptions in Java

answered Nov 17 '19 at 18:59

Rauf Aghayev

300
1
12

Throws and throw in same method

2 Answers2