Is it considered a bad practice to handle failed scenarios using exceptions?

Question

My simple definition is usually:
Fail response - when a process failes to complete due to missing parameters Error response - when a process breaks due to unknown/unexpected reason.

Now, breaking the process flow over bad parameters (e.g. missing mandatory fields) is very easy to do (in java). At any given point you can just throw an exception with a code or a message.

Yet, usually people have the notion that you should use exceptions only in exceptional cases, meaning cases which you do not plan in the algorithm.

What are the cons of planning failed scenarios using exceptions

Related: http://stackoverflow.com/questions/12923302/good-practices-for-java-exceptions-handling — Sandeep Chatterjee, May 15 '14 at 16:04

score 0 · Answer 1 · answered May 15 '14 at 16:06

Using exceptions for expected extraordinary cases is greatly inefficient. Exceptions are a poor choice for normal data paths in your software. The only case I would consider it a valid path is if this a backwater case in your program and you consider it very low traffic. There is an InvalidParamterException but it is "This exception, designed for use by the JCA/JCE engine classes"

Is it considered a bad practice to handle failed scenarios using exceptions?

1 Answers1